dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2025-10731

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-23
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 ReviewX – WooCommerce Product Reviews with Multi-Criteria, Reminder Emails, Google Reviews, Schema & More plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.2.12 via the allReminderSettings function. This makes it possible for unauthenticated attackers to obtain authentication tokens and subsequently bypass admin restrictions to access and export sensitive data including order details, names, emails, addresses, phone numbers, and user information.

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 ReviewX WooCommerce plugin versions up to 2.2.12 contain an insecure direct object reference (IDOR) vulnerability in the allReminderSettings function that allows unauthenticated attackers to retrieve authentication tokens and bypass admin restrictions, exposing sensitive customer PII including order details, names, emails, addresses, phone numbers, and user information.

MitigationUpdate the ReviewX plugin to version 2.2.13 or later immediately to patch the vulnerability. Review server access logs for signs of exploitation and notify affected users if data was accessed.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Confirm ReviewX plugin is installed
    Check if the ReviewX plugin directory exists in your WordPress installation at wp-content/plugins/reviewx/ or list installed plugins via wp-admin > Plugins
    Affected if ReviewX plugin is present in the WordPress installation
  2. Identify the installed ReviewX version
    Open the main plugin file (reviewx.php) in wp-content/plugins/reviewx/ and look for the 'Version' header in the plugin comment block, or check the readme.txt file for the 'Stable tag' value
    Affected if The version number is 2.2.12 or lower (any version 'up to' 2.2.12)
  3. Locate the vulnerable allReminderSettings function
    Search the plugin files for the string 'allReminderSettings' in wp-content/plugins/reviewx/ - typically found in includes or admin controller files
    Affected if The function exists in the installed version, confirming the vulnerable code is present
  4. Verify unauthenticated access to the vulnerable endpoint
    If the plugin exposes a REST API endpoint for allReminderSettings, test access without authentication using a tool like curl: curl -s https://yourdomain.com/wp-json/reviewx/v1/... (adjust endpoint path based on actual plugin routing)
    Affected if The endpoint returns authentication tokens or sensitive data without requiring authentication
  5. Check for unauthorized access in server logs
    Review web server access logs (Apache/nginx) for requests to the allReminderSettings endpoint from unauthenticated IPs, looking for patterns that indicate data exfiltration
    Affected if Unauthenticated requests to the vulnerable function are present in logs

A user is affected if the ReviewX plugin version is 2.2.12 or lower and the allReminderSettings function is accessible without authentication, allowing exposure of customer PII.

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 ReviewX plugin to version 2.2.13 or later immediately to patch the vulnerability. Review server access logs for signs of exploitation and notify affected users if data was accessed.

Recommended fix High confidence

ReviewX version 2.2.13 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the ReviewX plugin in the list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is running version 2.2.13 or higher
  6. 6. Test that the review and reminder features still function correctly

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

Have this fixed 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 help mitigating

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-2025-10731 — 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-2025-10731 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