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

CVE-2026-3355

MEDIUM · 6.1 CVSS v3.1 Published 2026-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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
The Customer Reviews for WooCommerce plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘crsearch’ parameter in all versions up to, and including, 5.101.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

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 for WordPress is vulnerable to Reflected Cross-Site Scripting (XSS) via the 'crsearch' parameter in versions up to 5.101.0. The vulnerability stems from insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject arbitrary web scripts through malicious links that trick users into clicking them.

MitigationUpdate the Customer Reviews for WooCommerce plugin to a version beyond 5.101.0 that includes proper sanitization of the 'crsearch' parameter using WordPress sanitization functions (e.g., sanitize_text_field) and appropriate output escaping before rendering user-supplied 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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Check the installed plugin version
    Navigate to WordPress Admin > Plugins > Installed Plugins, locate 'Customer Reviews for WooCommerce', and read the version number displayed. Alternatively, access the plugin file via FTP or file manager at wp-content/plugins/customer-reviews-for-woocommerce/customer-reviews-for-woocommerce.php and look for the 'Version:' header in the plugin comments.
    Affected if The version listed is 5.101.0 or any earlier version.
  2. Verify the plugin is active
    In WordPress Admin > Plugins, confirm that the Customer Reviews for WooCommerce plugin shows as 'Active'. Alternatively, check the wp_options table for the option 'crforplugin_active' set to 'yes'.
    Affected if The plugin is active and processing requests.
  3. Identify if the crsearch parameter is processed
    Locate the plugin file that handles search functionality (typically in the plugin's main PHP file or a file related to review submission/search). Search for code that reads 'crsearch' from GET or REQUEST superglobals (e.g., $_GET['crsearch'] or $_REQUEST['crsearch']).
    Affected if The plugin processes the 'crsearch' parameter without first sanitizing it.
  4. Inspect input sanitization on crsearch
    In the identified handler file, examine the code that processes the crsearch parameter. Look for WordPress sanitization functions such as sanitize_text_field(), sanitize_textarea_field(), or esc_html() applied to the crsearch value before use or output.
    Affected if No sanitization function (like sanitize_text_field) is applied to $_GET['crsearch'] or $_REQUEST['crsearch'] before the value is used or echoed.
  5. Inspect output escaping on crsearch
    Examine where the crsearch value is output or rendered in HTML. Look for proper escaping functions like esc_html(), esc_attr(), or esc_url() applied when the search value is displayed back to the user.
    Affected if The crsearch value is echoed or printed without escaping functions (esc_html, esc_attr) surrounding it.

A user is affected if the Customer Reviews for WooCommerce plugin version is 5.101.0 or earlier, the plugin is active, and the code handling the 'crsearch' parameter lacks proper sanitization with sanitize_text_field and output escaping with esc_html or esc_attr before rendering.

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

Update the Customer Reviews for WooCommerce plugin to a version beyond 5.101.0 that includes proper sanitization of the 'crsearch' parameter using WordPress sanitization functions (e.g., sanitize_text_field) and appropriate output escaping before rendering user-supplied data.

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-3355 — 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-3355 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