dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-3065

CRITICAL · 9.1 CVSS v3.1 Published 2025-04-24
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 Database Toolset plugin is vulnerable to arbitrary file deletion due to insufficient file path validation in a function in all versions up to, and including, 1.8.4. This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).

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 Database Toolset WordPress plugin has an arbitrary file deletion vulnerability in versions up to 1.8.4 due to insufficient path validation in a delete function. Unauthenticated attackers can traverse file paths and delete any file on the server, including critical files like wp-config.php, enabling full site compromise and potential RCE.

MitigationUpdate the Database Toolset plugin to version 1.8.5 or later which contains proper path validation. If immediate updating is not possible, consider removing the plugin or deploying a WAF rule to block suspicious file deletion requests.

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. Locate the Database Toolset plugin installation
    Check if the /wp-content/plugins/database-toolset/ directory exists on the server file system.
    Affected if The plugin directory exists, indicating the plugin is installed.
  2. Identify the installed plugin version
    Open the main plugin file (database-toolset.php) in the plugin directory and locate the version header comment at the top of the file, or check the readme.txt file for the Version field.
    Affected if The version listed is 1.8.4 or any earlier version (e.g., 1.8.3, 1.8.2, etc.).
  3. Verify if the plugin is active
    In the WordPress admin dashboard, go to Plugins > Installed Plugins and check whether Database Toolset shows as 'Active', or query the wp_options table for the option_name 'active_plugins' and check if it contains 'database-toolset'.
    Affected if The plugin is currently active, making the vulnerable function accessible to unauthenticated requests.
  4. Confirm the vulnerable file operation function exists
    Examine the plugin PHP files for functions that handle file deletion operations (commonly named with terms like delete_file, remove_file, or similar) and verify they lack path validation logic.
    Affected if The plugin contains file operation functions without proper path validation checks.

A user is affected if the Database Toolset plugin is installed at version 1.8.4 or earlier and is currently active, allowing the vulnerable file deletion function to be reachable by unauthenticated requests.

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 Database Toolset plugin to version 1.8.5 or later which contains proper path validation. If immediate updating is not possible, consider removing the plugin or deploying a WAF rule to block suspicious file deletion requests.

Recommended fix Moderate confidence

1.8.5 or latest available version

  1. 1. Backup the WordPress site and database before making any changes
  2. 2. Navigate to the WordPress admin dashboard > Plugins
  3. 3. Locate the 'Database Toolset' plugin in the installed plugins list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. If no update appears in the WordPress admin, visit the plugin page at wordpress.org/plugins/database-toolset/ and download the latest version
  6. 6. Deactivate the existing Database Toolset plugin
  7. 7. Delete the existing Database Toolset plugin files via Plugins > Installed Plugins > Delete
  8. 8. Upload and install the latest version of the plugin
Caveat Review plugin settings after upgrade as configuration may need adjustment

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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