dbcve.org
Customer Reviews For WoocommerceWordPress extension · Cusrev

CVE-2022-38134

HIGH · 8.8 CVSS v3.1 Published 2022-09-23
Fix available
A fix is available. Upgrade to after 5.3.5 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Authenticated (subscriber+) Broken Access Control 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 a Broken Access Control vulnerability exploitable by authenticated users with subscriber-level privileges or higher. This allows lower-privileged users to perform actions or access resources that should be restricted to higher-privileged roles, likely through missing or insufficient capability checks in specific plugin functions.

MitigationUpdate the Customer Reviews for WooCommerce plugin to a version newer than 5.3.5. Review user role capabilities and ensure only appropriate roles have access to plugin settings and review management functions.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify plugin installation status
    Navigate to WordPress admin > Plugins and locate 'Customer Reviews for WooCommerce' (Cusrev), or check the plugin files in wp-content/plugins/customer-reviews-for-woocommerce/ for the main plugin file containing version metadata
    Affected if The plugin is installed and active in WordPress/WooCommerce
  2. Verify installed version
    Check the plugin version displayed in the WordPress plugins list, or open the main plugin PHP file (e.g., customer-reviews-for-woocommerce.php) and locate the version header in the plugin comments
    Affected if The installed version is 5.3.5 or any version lower (e.g., 5.3.4, 5.3.3, etc.)
  3. Enumerate user roles with access
    In WordPress admin, go to Users > Users List and review the roles assigned to each user account. Alternatively, check via Users > Roles if a role editor plugin is available
    Affected if There exist one or more users with the Subscriber role, or any role ranked below Administrator/Editor that has access to the site
  4. Check plugin capability settings
    Navigate to the plugin settings page (usually under WooCommerce > Reviews or a dedicated Customer Reviews menu item) and examine where user role permissions are defined, if such settings exist
    Affected if The plugin exposes review management, settings modification, or bulk actions to users without verifying elevated capabilities (Administrator/Editor level)
  5. Test for privilege escalation via plugin functions
    Using a browser or HTTP tool, attempt to access plugin admin pages or trigger plugin AJAX actions while logged in as a Subscriber-level user; observe whether access is granted when it should be denied
    Affected if A user with Subscriber role can access plugin functions, admin pages, or modify reviews/settings that require higher privileges

You are affected if the Customer Reviews for WooCommerce plugin version is 5.3.5 or lower AND your site has at least one user with Subscriber-level privileges or higher who can trigger the vulnerable plugin functions.

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
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. Review user role capabilities and ensure only appropriate roles have access to plugin settings and review management functions.

Recommended fix High confidence

Customer Reviews for WooCommerce version 5.3.6 or latest available version

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Customer Reviews for WooCommerce' plugin
  4. Check if current version is 5.3.5 or lower
  5. If vulnerable, click 'Update Now' to install the latest version
  6. Alternatively, manually download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the new version number in the plugins list
  8. Test that the plugin functionality works correctly

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

Fix this in Customer Reviews For Woocommerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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