dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-60171

HIGH · 7.1 CVSS v3.1 Published 2025-09-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in yourplugins Conditional Cart Messages for WooCommerce – YourPlugins.com yourplugins-wc-conditional-cart-notices allows Stored XSS.This issue affects Conditional Cart Messages for WooCommerce – YourPlugins.com: from n/a through <= 1.2.10.

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 confidence

CSRF vulnerability in the Conditional Cart Messages for WooCommerce plugin allows attackers to trick authenticated administrators into submitting malicious requests that inject XSS payloads into cart message settings. The injected payloads are stored and execute when users view those cart messages.

MitigationUpdate to version >1.2.10 if available; otherwise implement CSRF token validation on all form submissions and AJAX endpoints, and ensure all user-supplied message content is properly sanitized before storage and output.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Conditional Cart Messages for WooCommerce plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Conditional Cart Messages for WooCommerce' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'conditional-cart-messages-for-woocommerce' or similar.
    Affected if The plugin appears in the installed plugins list
  2. Determine the installed plugin version
    In WordPress admin Plugins page, click on the plugin name to view its details, or check the plugin's main PHP file header for the 'Version' comment. The affected versions are <=1.2.10.
    Affected if The installed version is 1.2.10 or lower, or if the version cannot be determined (older installation)
  3. Verify WooCommerce is active
    In WordPress admin, go to Plugins and confirm WooCommerce is installed and activated. This plugin is a WooCommerce extension and requires WooCommerce to function.
    Affected if WooCommerce is active and the vulnerable plugin is installed
  4. Inspect cart message settings for suspicious content
    Navigate to WooCommerce > Cart Messages or the plugin's settings page. Examine any custom cart message fields (such as condition-based messages, cart notices, or custom message content). Look for any unexpected script tags, javascript: URLs, img onerror attributes, or other XSS payload patterns in the message content.
    Affected if Any cart message settings contain unsanitized HTML, script tags, or XSS-like payloads that were not intentionally added by the administrator

The environment is affected if the Conditional Cart Messages for WooCommerce plugin is installed with version 1.2.10 or lower and cart message settings contain stored XSS payloads.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version >1.2.10 if available; otherwise implement CSRF token validation on all form submissions and AJAX endpoints, and ensure all user-supplied message content is properly sanitized before storage and output.

Recommended fix Moderate confidence

1.2.11 or later (upgrade to the latest available version from WordPress.org or YourPlugins.com)

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Find 'Conditional Cart Messages for WooCommerce' by YourPlugins.com.
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version.
  5. 5. Alternatively, you can manually download the updated plugin from WordPress.org or YourPlugins.com and reinstall.
  6. 6. After updating, verify the plugin is functioning correctly by testing cart conditional message functionality.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-60171 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-60171 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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