LiveActive security incident?Get immediate response
CVE Record

CVE-2026-3353: Comment SPAM Wiper <= 1.2.1 - Authenticated (Administrator+) Stored Cross-Site Scripting via 'API Key' Setting

The Comment SPAM Wiper plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'API Key' setting in all versions up to, and including, 1.2.1. This is due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Administrator-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.

MediumCVSS 4.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-3353 is a stored cross-site scripting issue in the WordPress Comment SPAM Wiper plugin through version 1.2.1. It requires an authenticated Administrator-level user and only applies to multisite installations or sites where unfiltered_html is disabled. Business urgency is moderate: abuse requires high privilege, but successful injection can run script when affected admin pages are viewed.

Executive priority

Treat as a medium-priority WordPress hygiene issue. Prioritize sites with shared administration, multisite deployments, or recent admin account compromise concerns. It is not currently supported by public evidence of active exploitation, but stored XSS can support account abuse and administrative session targeting.

Technical view

The plugin insufficiently sanitizes and escapes the 'API Key' setting, allowing Administrator+ users to store arbitrary web script that executes when an injected page is accessed. The CVSS 3.1 score is 4.4 with high privileges and high attack complexity. The issue is classified as CWE-79 and is reported for versions up to and including 1.2.1.

Likely exposure

Exposure is limited to WordPress sites running Comment SPAM Wiper <= 1.2.1, specifically multisite environments or installations where unfiltered_html has been disabled. Sites without the plugin, non-affected configurations, or deployments without untrusted Administrator-level users are less exposed.

Exploitation context

No active exploitation is indicated in the provided sources, and the CVE is not listed as KEV. Practical abuse requires Administrator-level access, making this more relevant to compromised admin accounts, delegated admin models, or environments where administrators are not fully trusted.

Researcher notes

The bundle cites Wordfence and WordPress plugin Trac references for admin.php around the vulnerable setting. The affected-version metadata appears limited, while the title and description state all versions through 1.2.1. No fixed version or vendor patch details are provided in the supplied sources.

Mitigation direction

  • Inventory WordPress sites for the Comment SPAM Wiper plugin and installed version.
  • Check vendor or WordPress plugin guidance for an official fixed release or removal recommendation.
  • Disable or remove the plugin if it is unnecessary or cannot be safely updated.
  • Restrict Administrator-level access to trusted users only.
  • Review multisite and unfiltered_html configurations for affected exposure conditions.

Validation and detection

  • Confirm whether Comment SPAM Wiper is installed on each WordPress site.
  • Identify plugin versions up to and including 1.2.1.
  • Determine whether the site is multisite or has unfiltered_html disabled.
  • Review the API Key setting for unexpected script-like content.
  • Check web logs and admin activity for unusual plugin settings changes.
Prepared
Confidence
medium
Sources
5

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-2026-3353 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
Medium
CVSS
4.4 (3.1)
Known Exploited
No
Published

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

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
4Source 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
4.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N1.32.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.4Medium
CVSS 3.1 vector shape for CVE-2026-3353Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
intermodComment SPAM Wiper0unaffected
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.