dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-13771

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 weeks old

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
The Customer Reviews for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'color' Shortcode Attribute in all versions up to, and including, 5.113.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 confidence

The Customer Reviews for WooCommerce plugin fails to sanitize the 'color' parameter in its shortcode and does not escape output properly, allowing authenticated users with contributor-level access or higher to inject malicious JavaScript that executes when other users view the affected page.

MitigationUpdate the plugin to version 5.113.1 or later, which includes proper input sanitization using functions like sanitize_hex_color() and output escaping with esc_attr() for the color shortcode attribute.

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

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. Locate the Customer Reviews for WooCommerce plugin
    Check your WordPress installation under wp-content/plugins/ for a folder named 'customer-reviews-for-woocommerce' or similar. Open the main plugin PHP file and look for the version comment or the Version: header in the file comments.
    Affected if The plugin is installed and you cannot confirm it is version 5.113.1 or later.
  2. Verify the installed version
    Open the main plugin file (usually the primary PHP file in the plugin directory) and locate the version string in the plugin header comment. Compare this version to 5.113.1.
    Affected if The installed version is lower than 5.113.1, or you cannot determine the version.
  3. Identify shortcode usage in content
    Search your WordPress database or content files for occurrences of the shortcode [cusrev] or [customer_reviews] that include a 'color' attribute, such as [cusrev color="..."]
    Affected if The shortcode with the color parameter is present in any post, page, or widget content.
  4. Check for contributor-level or higher user accounts
    Review your WordPress user roles and identify any accounts with Contributor, Author, Editor, or Administrator roles, as these roles can access the shortcode functionality.
    Affected if There are user accounts with Contributor-level access or higher who could potentially craft malicious shortcode content.

You are affected if the Customer Reviews for WooCommerce plugin is installed at a version lower than 5.113.1 AND the shortcode with a color parameter is in use on your site, allowing any authenticated contributor-level user to inject malicious scripts.

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 the plugin to version 5.113.1 or later, which includes proper input sanitization using functions like sanitize_hex_color() and output escaping with esc_attr() for the color shortcode attribute.

Recommended fix Moderate confidence

5.114.0 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Customer Reviews for WooCommerce' plugin
  4. Check the current version is 5.113.0 or lower
  5. Update the plugin to the latest available version (5.114.0 or higher)

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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