LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32544: WordPress OOPSpam Anti-Spam plugin <= 1.2.62 - Cross Site Scripting (XSS) vulnerability

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in OOPSpam Team OOPSpam Anti-Spam oopspam-anti-spam allows Stored XSS.This issue affects OOPSpam Anti-Spam: from n/a through <= 1.2.62.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-32544 is a stored cross-site scripting issue in the WordPress OOPSpam Anti-Spam plugin through version 1.2.62. A successful attack could cause malicious script to run in a user’s browser when they view affected content. No source provided confirms active exploitation.

Executive priority

Treat as a high-priority WordPress plugin exposure for sites using OOPSpam Anti-Spam. Prioritize inventory and update decisions, especially for public-facing sites. There is no cited evidence of active exploitation, but stored XSS can affect users and site trust.

Technical view

The CVE describes CWE-79 improper input neutralization during web page generation in oopspam-anti-spam. CVSS 3.1 is 7.1, vector AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L. The issue is stored XSS and affects OOPSpam Anti-Spam through <= 1.2.62.

Likely exposure

Exposure is limited to WordPress sites running OOPSpam Anti-Spam version 1.2.62 or earlier. Sites allowing untrusted input that is later rendered in administrative or user-facing pages may face higher practical risk.

Exploitation context

The CVSS vector indicates network access, low attack complexity, no privileges required, and user interaction required. The source bundle marks KEV as false, and no cited source states active exploitation or provides public exploit status.

Researcher notes

Evidence is limited to the CVE record and Patchstack reference. The bundle does not name a fixed version or detailed vulnerable parameter. Avoid assuming exploitability beyond stored XSS properties and the CVSS vector. Monitor sources for updated technical details.

Mitigation direction

  • Inventory WordPress sites for the OOPSpam Anti-Spam plugin and installed version.
  • If version is <= 1.2.62, check vendor and Patchstack guidance for a fixed release.
  • Apply vendor-supported updates when available and test site functionality afterward.
  • If no fix is available, consider disabling the plugin until vendor guidance is clear.
  • Limit administrative exposure and review who can view plugin-processed content.

Validation and detection

  • Confirm the plugin slug is oopspam-anti-spam on each WordPress site.
  • Verify installed versions are greater than 1.2.62, if a fixed version exists.
  • Review Patchstack and CVE records for updated remediation details.
  • Check web server and WordPress logs for unusual script-like submissions.
  • Confirm no untrusted stored content is rendered in privileged user sessions.
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-2026-32544 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-2026-32544Attack 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
OOPSpam TeamOOPSpam Anti-Spamoopspam-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.