CVE-2025-28883
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Martin WP Compare Tables wp-compare-tables allows Stored XSS.This issue affects WP Compare Tables: from n/a through <= 1.0.5.
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 · high confidenceCross-Site Request Forgery (CSRF) vulnerability in the WP Compare Tables plugin allows authenticated attackers to inject malicious scripts through stored XSS. By tricking a logged-in administrator into visiting a crafted page, attackers can execute arbitrary JavaScript in the context of the vulnerable site, compromising user sessions and data.
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 plugin installationCheck if the WP Compare Tables plugin is installed in your WordPress environment by reviewing the plugins directory (wp-content/plugins/) or via WordPress admin panel under PluginsAffected if WP Compare Tables plugin is present in the installation
-
Determine installed versionCheck the plugin version by viewing the main plugin file header (e.g., wp-content/plugins/wp-compare-tables/wp-compare-tables.php) or through WordPress admin Plugins pageAffected if Installed version is unknown or falls within a vulnerable range (compare against any official advisory)
-
Identify vulnerable featureReview plugin code for state-changing operations (form submissions, AJAX actions, settings updates) that lack nonce verification. Look for functions handling user input that may be stored and displayed without sanitizationAffected if State-changing operations lack anti-CSRF nonce validation or user inputs are not properly sanitized before storage/display
-
Inspect stored XSS entry pointsSearch plugin source code for output functions (echo, print, etc.) that render user-supplied data without proper escaping (esc_html, esc_attr, etc.)Affected if User-controlled data is stored and rendered without sanitization, enabling stored XSS execution
-
Verify session impactConfirm that administrative actions can be triggered via crafted requests, allowing session compromise through JavaScript injectionAffected if Administrator session can be compromised via malicious JavaScript execution through the vulnerability
User is affected if WP Compare Tables plugin is installed and the vulnerable code paths lack CSRF nonce protection and proper input sanitization allowing stored XSS execution.
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 anti-CSRF tokens (nonces) on state-changing operations and properly sanitize/validate all user inputs and outputs to prevent XSS execution.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-28883 — 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-2025-28883 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