CVE-2026-32544
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceStored Cross-Site Scripting (XSS) vulnerability in OOPSpam Anti-Spam plugin versions up to 1.2.62 allows attackers to inject malicious JavaScript scripts that are persistently stored on the server. When users view affected pages, the injected script executes in their browsers, potentially stealing session cookies, credentials, or performing actions on behalf of victims.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if OOPSpam Anti-Spam plugin is installedAccess WordPress admin panel, go to Plugins > Installed Plugins, or inspect /wp-content/plugins/ directory for a folder named 'oo-spam' or similar OOPSpam-related folderAffected if OOPSpam Anti-Spam plugin is found in the WordPress installation
-
Determine installed plugin versionIn WordPress admin, click on the plugin to view its details and find the version number, or read the main plugin PHP file header for 'Version:' fieldAffected if Version number is 1.2.62 or lower (any version up to and including 1.2.62)
-
Verify plugin is actively processing user submissionsCheck WordPress settings for OOPSpam configuration - confirm the plugin is enabled and active for form submissions (check /wp-admin/options-general.php?page=oo-spam or similar settings page)Affected if Plugin is installed, version is vulnerable, and plugin is actively processing form submissions that accept user input
-
Inspect stored data for potential XSS payloadsExamine WordPress database tables where OOPSpam stores submissions (typically posts, comments, or custom tables created by the plugin) for suspicious patterns like '<script', 'javascript:', 'onerror=', 'onload=' or encoded variantsAffected if Database contains user-submitted content with script tags, event handlers, or JavaScript URIs that are not properly sanitized
User is affected if OOPSpam Anti-Spam plugin is installed with version 1.2.62 or lower and the plugin is actively handling user-submitted content that could be stored and rendered without sanitization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper input validation and output encoding/sanitization on all user-supplied data before storage and before rendering in web pages. Validate that stored content does not contain script tags or other HTML/JavaScript elements.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32544 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32544 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data