CVE-2025-23471
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 etemplates ECT Add to Cart Button ect-add-to-cart-button allows Stored XSS.This issue affects ECT Add to Cart Button: from n/a through <= 1.4.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the ECT Add to Cart Button WordPress plugin allows attackers to inject malicious JavaScript via Stored XSS. By tricking authenticated administrators into visiting crafted pages, attackers can force unintended form submissions that store malicious scripts, which then execute when other users view the affected cart button content.
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.
-
Verify plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'ECT Add to Cart Button' or check the plugin files in wp-content/plugins/ for the plugin directory nameAffected if Plugin is installed and active
-
Get installed version numberIn WordPress admin Plugins page, click 'View Details' on the ECT Add to Cart Button plugin to see the version number, or read the main plugin PHP file and look for the 'Version' header in the plugin comment blockAffected if Version is at or below the known vulnerable version (compare to official WordPress security advisory for exact version range)
-
Inspect admin form submissions for nonce protectionExamine the plugin PHP source code (main plugin file and any files handling form actions) and search for wp_nonce_field, wp_verify_nonce, or check_admin_referer calls on form handlers that process cart button configurationsAffected if Forms that save cart button settings lack nonce verification (no nonce field in form and no nonce check in handler)
-
Inspect stored data for sanitizationReview plugin code that saves user-supplied input (especially fields for button text, URLs, or custom content) and verify that sanitization functions like sanitize_text_field, esc_attr, or wp_kses are called before inserting data into the databaseAffected if User-supplied cart button data is stored without sanitization functions
-
Inspect output for XSS protectionReview plugin code that displays cart button content on the frontend and verify that output is escaped using functions like esc_html, esc_attr, or esc_url before being renderedAffected if Cart button content is output without proper escaping functions
The environment is affected if the ECT Add to Cart Button plugin is installed without proper nonce validation on admin forms AND without sanitization/escaping of stored cart button data, allowing stored XSS to persist.
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 all admin form submissions and AJAX actions, validate request origins, and sanitize all user-supplied input before storage and output.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23471 — 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-23471 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