LiveActive security incident?Get immediate response
CVE Record

CVE-2023-48272: WordPress Maspik – Spam blacklist Plugin <= 0.9.2 is vulnerable to Cross Site Scripting (XSS)

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in yonifre Maspik – Spam Blacklist allows Stored XSS.This issue affects Maspik – Spam Blacklist: from n/a through 0.9.2.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a stored cross-site scripting issue in the WordPress Maspik – Spam Blacklist plugin through version 0.9.2. Malicious input could be saved and later run in another user’s browser when viewed. That can affect confidentiality, integrity, and availability at a limited level.

Executive priority

Treat as a high-priority WordPress plugin exposure where the plugin is active. Prioritize public-facing sites and administrative workflows that regularly review spam or blacklist data. No active exploitation is evidenced in the provided sources.

Technical view

CVE-2023-48272 is CWE-79 improper output neutralization in yonifre Maspik – Spam Blacklist, package contact-forms-anti-spam. The CVSS 3.1 vector is 7.1 high: network reachable, low complexity, no privileges required, user interaction required, scope changed, with low CIA impact.

Likely exposure

Exposure is most likely on WordPress sites running Maspik – Spam Blacklist/contact-forms-anti-spam version 0.9.2 or earlier. The provided data does not identify other affected products or hosting environments.

Exploitation context

The source bundle does not show CISA KEV listing or cited active exploitation. The CVSS vector indicates a remote attacker needs no account, but a user must view affected stored content for browser-side impact.

Researcher notes

The provided evidence names stored XSS but does not describe the exact sink, triggering page, patched version, or exploit maturity. Avoid assuming a fix version or exploit availability beyond the CVE and Patchstack record.

Mitigation direction

  • Inventory WordPress sites for Maspik – Spam Blacklist/contact-forms-anti-spam installations.
  • If version is 0.9.2 or earlier, check vendor or Patchstack guidance immediately.
  • Upgrade to a vendor-recommended fixed release if one is available.
  • Disable or remove the plugin where no safe vendor guidance is available.
  • Review stored plugin data for suspicious script-like content before re-enabling.

Validation and detection

  • Confirm plugin package name and displayed version on each WordPress site.
  • Compare installed versions against affected range through 0.9.2.
  • Check whether the plugin is active, not merely installed.
  • Review recent form submissions and blacklist entries for suspicious HTML or script content.
  • Check security monitoring for unusual admin browser activity after viewing plugin data.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-48272 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2023-48272Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
yonifreMaspik – Spam Blacklistcontact-forms-anti-spam, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.