dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-10726

CRITICAL · 9.1 CVSS v3.1 Published 2025-10-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 WPRecovery plugin for WordPress is vulnerable to SQL Injection via the 'data[id]' parameter in all versions up to, and including, 2.0. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Additionally, the result of this SQL injection is passed directly to PHP's unlink() function, allowing attackers to delete arbitrary files on the server by injecting file paths through the SQL query.

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 WPRecovery WordPress plugin up to version 2.0 has a critical SQL injection vulnerability in the 'data[id]' parameter. The user-supplied input is not properly escaped and the SQL query lacks prepared statements, allowing unauthenticated attackers to inject arbitrary SQL. Additionally, the query result is directly passed to PHP's unlink() function, enabling unauthenticated attackers to delete arbitrary files on the server by injecting file paths through SQL.

MitigationUpgrade to the latest version of WPRecovery plugin which should contain proper input sanitization and prepared SQL statements. Until then, disable the plugin or implement web application firewall rules to block requests containing suspicious 'data[id]' values.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Confirm WPRecovery plugin is installed
    Check the WordPress plugins directory for the wprecovery folder. In the WordPress admin, go to Plugins > Installed Plugins and look for WPRecovery. Alternatively, inspect the filesystem at /wp-content/plugins/ for a folder named 'wprecovery' or similar.
    Affected if The WPRecovery plugin folder exists in the WordPress plugins directory and the plugin is active.
  2. Determine the installed version
    Open the main plugin PHP file (usually wprecovery.php or similar in the plugin folder) and locate the version comment or header. Alternatively, check the readme.txt file in the plugin folder for the 'Stable tag' or 'Version' entry.
    Affected if The installed version is 2.0 or any version prior to 2.0 (the plugin versions up to 2.0 are affected).
  3. Verify the plugin handles the data[id] parameter
    Search the plugin PHP files for occurrences of 'data[id]' or '$_POST["data"]' or '$_REQUEST["data"]' to identify if the vulnerable parameter is processed. Look for SQL queries that directly use this parameter without prepared statements.
    Affected if The plugin code contains direct use of the 'data[id]' parameter in SQL queries without using $wpdb->prepare() or equivalent prepared statement functions.
  4. Confirm the unlink() call uses query results
    Search the plugin PHP files for 'unlink(' calls that receive input from database query results. Look for patterns where query results (from SELECT statements) are passed as the file path to unlink().
    Affected if The plugin contains code that passes database query results directly to PHP's unlink() function without validation.

You are affected if the WPRecovery plugin is installed, active, and running version 2.0 or earlier with the vulnerable code path handling the data[id] parameter accessible to unauthenticated users.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to the latest version of WPRecovery plugin which should contain proper input sanitization and prepared SQL statements. Until then, disable the plugin or implement web application firewall rules to block requests containing suspicious 'data[id]' values.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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