dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-10679

HIGH · 7.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 →
82/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
The ReviewX – WooCommerce Product Reviews with Multi-Criteria, Reminder Emails, Google Reviews, Schema & More plugin for WordPress is vulnerable to arbitrary method calls in all versions up to, and including, 2.2.12. This is due to insufficient input validation in the bulkTenReviews function that allows user-controlled data to be passed directly to a variable function call mechanism. This makes it possible for unauthenticated attackers to call arbitrary PHP class methods that take no inputs or have default values, potentially leading to information disclosure or remote code execution depending on available methods and server configuration.

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 WordPress plugin contains a vulnerability in the bulkTenReviews function where insufficient input validation allows user-controlled data to be passed directly to PHP variable function calls. Unauthenticated attackers can exploit this to invoke arbitrary class methods that require no parameters or have default values, potentially achieving information disclosure or remote code execution depending on what methods are available in the plugin or loaded via WordPress.

MitigationUpdate the ReviewX plugin to version 2.2.13 or later which contains the patch. If immediate updating is not feasible, consider temporarily disabling the plugin or deploying WAF rules to block requests targeting the vulnerable function.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 ReviewX plugin is installed
    Check for the ReviewX plugin in your WordPress installation by looking for the reviewx directory under wp-content/plugins/, or via WordPress admin under Plugins > Installed Plugins
    Affected if ReviewX plugin is present in the WordPress installation
  2. Determine installed ReviewX version
    Open the main plugin file (reviewx.php) in the reviewx plugin directory and locate the Version header in the file comments, or view the version in WordPress admin under Plugins > Installed Plugins > ReviewX
    Affected if Installed version is lower than 2.2.13 (the patched version)
  3. Confirm plugin is active
    Check the plugin status in WordPress admin under Plugins > Installed Plugins, or query the wp_options table for the active_plugins option containing 'reviewx'
    Affected if ReviewX plugin is active in the WordPress environment
  4. Verify the vulnerable endpoint is accessible
    Check if the WordPress AJAX endpoint /wp-admin/admin-ajax.php exposes the bulkTenReviews action, or inspect the plugin source for the bulkTenReviews function to confirm it handles unauthenticated requests
    Affected if The bulkTenReviews function handles requests without authentication and without strict validation on the method parameter

If ReviewX is installed, active, version is below 2.2.13, and the bulkTenReviews function handles unauthenticated requests, the environment is affected by CVE-2025-10679

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 which contains the patch. If immediate updating is not feasible, consider temporarily disabling the plugin or deploying WAF rules to block requests targeting the vulnerable function.

Recommended fix Moderate confidence

Latest version of ReviewX plugin (version 2.2.13 or higher)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the ReviewX plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/reviewx/ and upload via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is functioning correctly on the site

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-10679 — 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-10679 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