Customer Reviews For WoocommerceWordPress extension · Cusrev
CVE-2022-38470
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 · uneditedCross-Site Request Forgery (CSRF) 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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the Customer Reviews for WooCommerce plugin versions 5.3.5 and earlier allows attackers to trick authenticated users into performing unintended actions by leveraging the lack of proper nonce validation in the plugin's forms or AJAX requests.
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
<= 5.3.5CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm the plugin is installedNavigate to WordPress admin > Plugins and look for 'Customer Reviews for WooCommerce' or 'Cusrev Customer Reviews For Woocommerce' in the installed plugins listAffected if The plugin appears in the installed plugins list
-
Check the installed plugin versionIn the Plugins page, click on the plugin to view its details, or check the plugin header comment in the main plugin file (typically /wp-content/plugins/customer-reviews-for-woocommerce/ or similar)Affected if The displayed version number is 5.3.5 or lower
-
Verify the plugin is activeOn the Plugins admin page, confirm the plugin shows as 'Active' rather than 'Inactive'Affected if The plugin status shows Active
-
Identify exposed AJAX endpointsInspect the plugin's PHP files for registered AJAX handlers using add_action('wp_ajax_...') or add_action('wp_ajax_nopriv_...') calls, particularly those handling form submissions or user reviewsAffected if AJAX endpoints exist that handle user submissions without visible nonce validation in the code
If the Customer Reviews for WooCommerce plugin is installed, active, and version 5.3.5 or lower, the environment is vulnerable to CSRF attacks via unauthenticated form or AJAX requests.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the Customer Reviews for WooCommerce plugin to a version newer than 5.3.5 which should include proper anti-CSRF nonce verification. If immediate update is not possible, consider disabling the plugin or implementing additional site-level CSRF protections.
Fix this in Customer Reviews For Woocommerce
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38470 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-38470 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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