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

CVE-2025-52783

HIGH · 7.1 CVSS v3.1 Published 2025-06-20
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 themelocation Change Cart button Colors WooCommerce wc-style allows Stored XSS.This issue affects Change Cart button Colors WooCommerce: from n/a through <= 1.0.

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 Change Cart button Colors WooCommerce plugin (wc-style) allows attackers to inject malicious scripts through stored XSS. The plugin lacks anti-CSRF tokens on forms handling cart button color settings, enabling authenticated administrators to be tricked into submitting crafted requests that store malicious JavaScript in the plugin's settings.

MitigationIf a patched version is unavailable, implement anti-CSRF tokens on all form submissions and add proper input sanitization and output encoding for the color settings to prevent stored XSS; alternatively, remove the plugin until a secure version is available.

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 the Change Cart button Colors plugin is installed
    Check your WordPress plugins directory or WooCommerce plugin list for 'Change Cart button Colors' or 'wc-style'
    Affected if The plugin named 'Change Cart button Colors' or 'wc-style' is present in the WordPress/WooCommerce installation
  2. Determine the installed plugin version
    Access the WordPress admin panel under Plugins > Installed Plugins and locate the version number for 'Change Cart button Colors' or check the plugin's main PHP file for the Version header
    Affected if The installed version falls within any vulnerable version range or is unknown/unpatched
  3. Verify if the cart button color settings forms lack anti-CSRF protection
    Inspect the plugin source code (typically in includes/admin or similar directories) and examine form handlers for cart button color settings; look for wp_nonce_field, verify_nonce, or CSRF token validation in the PHP files handling these settings
    Affected if The forms handling cart button color settings (e.g., button color, background color, text color options) contain no nonce verification or token validation logic
  4. Inspect stored plugin settings for malicious scripts
    Access WordPress database tables (typically wp_options) and query for plugin-related settings (look for options containing 'wc_style', 'cart_button_color', or similar); examine the stored values for any unexpected script tags, javascript: URIs, or encoded malicious content
    Affected if The plugin settings database entries contain unsanitized script tags, event handlers, or other XSS payloads in color-related fields
  5. Check WordPress activity logs for suspicious form submissions
    Review server access logs and WordPress audit logs for POST requests to the plugin's settings admin page that originated from unexpected referrers or contain anomalous parameter values in color fields
    Affected if There are form submission logs to the plugin settings that contain XSS payloads or originated from external/tricked administrators

A user is affected if the Change Cart button Colors (wc-style) plugin is installed and its cart button color settings forms lack anti-CSRF token validation, allowing stored XSS payloads to be injected into the plugin settings.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

If a patched version is unavailable, implement anti-CSRF tokens on all form submissions and add proper input sanitization and output encoding for the color settings to prevent stored XSS; alternatively, remove the plugin until a secure version is available.

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

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52783 — 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-52783 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