dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-4664

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
The Customer Reviews for WooCommerce plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 5.103.0. This is due to the `create_review_permissions_check()` function comparing the user-supplied `key` parameter against the order's `ivole_secret_key` meta value using strict equality (`===`), without verifying that the stored key is non-empty. For orders where no review reminder email has been sent, the `ivole_secret_key` meta is not set, causing `get_meta()` to return an empty string. An attacker can supply `key: ""` to match this empty value and bypass the permission check. This makes it possible for unauthenticated attackers to submit, modify, and inject product reviews on any product — including products not associated with the referenced order — via the REST API endpoint `POST /ivole/v1/review`. Reviews are auto-approved by default since `ivole_enable_moderation` defaults to `"no"`.

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 has an authentication bypass vulnerability in versions up to 5.103.0. The `create_review_permissions_check()` function compares a user-supplied `key` parameter against the order's `ivole_secret_key` meta value using strict equality (`===`), but fails to verify the stored key is non-empty. For orders where no review reminder email has been sent, the meta value returns empty string, allowing attackers to supply `key: ""` to bypass permission checks and submit/modify/inject reviews via REST API endpoint `POST /ivole/v1/review`. Reviews auto-approve by default.

MitigationUpdate the plugin to version 5.104.0 or later where the vendor has fixed the empty key validation. Until then, consider disabling the review submission REST API endpoint or implementing additional server-side validation.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 plugin version
    Locate the Customer Reviews for WooCommerce plugin in your WordPress installation (typically in wp-content/plugins/customer-reviews-for-woocommerce/) and read the main plugin file header to obtain the version number, or query it via WP-CLI: wp plugin list --name='customer-reviews-for-woocommerce' --format=json
    Affected if The installed version is 5.103.0 or lower
  2. Verify REST API endpoint accessibility
    Test whether the vulnerable endpoint responds by sending a POST request to /wp-json/ivole/v1/review (or /?rest_route=/ivole/v1/review) with a minimal payload such as {key: "", order_id: 1} - a 400/200 response indicates the endpoint is active
    Affected if The endpoint returns any HTTP response (not 404), confirming the plugin REST API is registered and reachable
  3. Check for orders with empty review keys
    Query the WooCommerce orders database for orders where the ivole_secret_key meta value is empty or does not exist: SELECT post_id FROM wp_postmeta WHERE meta_key = 'ivole_secret_key' AND (meta_value = '' OR meta_value IS NULL) for wp_posts with post_type = 'shop_order'; alternatively use WooCommerce REST API or admin interface
    Affected if Any orders exist with empty or missing ivole_secret_key meta values (typically orders that never received a review reminder email)
  4. Confirm default auto-approval setting
    Check the plugin settings in WooCommerce > Reviews > Settings (or similar) for the option that controls whether submitted reviews are auto-approved without moderation
    Affected if Reviews are configured to auto-approve (the default setting), allowing injected reviews to appear publicly without review

You are affected if the plugin version is 5.103.0 or lower, the /ivole/v1/review REST endpoint is accessible, and there are orders with empty ivole_secret_key values, combined with auto-approval enabled.

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.104.0 or later where the vendor has fixed the empty key validation. Until then, consider disabling the review submission REST API endpoint or implementing additional server-side validation.

Recommended fix Moderate confidence

Latest version after 5.103.0 (check wordpress.org for current stable release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Customer Reviews for WooCommerce' plugin
  4. 4. Check the current version installed (should be 5.103.0 or lower)
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. Alternatively, download the latest version from wordpress.org/plugins/ustomer-reviews-for-woocommerce/ and upload manually

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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