dbcve.org
Customer Reviews For WoocommerceWordPress extension · Cusrev

CVE-2022-40194

HIGH · 7.5 CVSS v3.1 Published 2022-09-23
Fix available
A fix is available. Upgrade to after 5.3.5 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Unauthenticated Sensitive Information Disclosure vulnerability in Customer Reviews for WooCommerce plugin <= 5.3.5 at WordPress

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 versions 5.3.5 and below contain an unauthenticated sensitive information disclosure vulnerability. Attackers can exploit this to access sensitive data without requiring any authentication credentials.

MitigationUpdate the Customer Reviews for WooCommerce plugin to a version newer than 5.3.5. If immediate update is not possible, restrict access to the affected endpoint via web server configuration or disable the plugin temporarily until a patch can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Customer Reviews For WoocommerceWordPress extension
Affected:<= 5.3.5

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Verify the plugin is installed
    Check your WordPress site's wp-content/plugins/ directory for a folder named 'customer-reviews-woocommerce' or similar Cusrev plugin folder. In WordPress admin, go to Plugins > Installed Plugins and look for 'Customer Reviews for WooCommerce'.
    Affected if The plugin folder exists in your WordPress installation or appears in the WordPress admin plugin list.
  2. Determine the installed version
    In WordPress admin, go to Plugins > Installed Plugins and find 'Customer Reviews for WooCommerce'. The version number is displayed below the plugin name. Alternatively, open the main plugin PHP file (usually in wp-content/plugins/customer-reviews-woocommerce/) and look for a 'Version' header in the plugin comment block.
    Affected if The displayed version number is 5.3.5 or lower.
  3. Confirm the vulnerable endpoint is reachable
    The vulnerability exploits an unauthenticated endpoint. Use a web browser or curl to attempt访问 /?wc-ajax=... or similar Cusrev-related AJAX endpoints without providing authentication. Check your server access logs for requests to paths containing 'cusrev', 'customer-reviews', or 'wc-ajax' endpoints related to the plugin.
    Affected if The endpoint responds without requiring login credentials or authentication tokens.
  4. Check for sensitive data exposure
    Review any publicly accessible pages that display customer review data. Look for unintended exposure of customer emails, order details, or other personally identifiable information that should require authentication to access.
    Affected if Sensitive customer data (email addresses, order numbers, customer names) is visible without being logged in.

Your environment is affected if the Customer Reviews for WooCommerce plugin is installed with version 5.3.5 or lower and the vulnerable unauthenticated endpoint is accessible on your site.

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
Upgrade available Upgrade to a release after 5.3.5
Interim mitigation

Update the Customer Reviews for WooCommerce plugin to a version newer than 5.3.5. If immediate update is not possible, restrict access to the affected endpoint via web server configuration or disable the plugin temporarily until a patch can be applied.

Fix this in Customer Reviews For Woocommerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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