dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-7645

HIGH · 8.1 CVSS v3.1 Published 2025-07-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

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 Extensions For CF7 (Contact form 7 Database, Conditional Fields and Redirection) plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the 'delete-file' field in all versions up to, and including, 3.2.8. This makes it possible for unauthenticated attackers to delete arbitrary files on the server, when an administrator deletes the submission, 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 Extensions For CF7 WordPress plugin lacks proper path validation in its 'delete-file' field functionality, allowing unauthenticated attackers to manipulate file deletion paths. By exploiting insufficient input sanitization, attackers can delete critical files like wp-config.php, potentially leading to remote code execution through site reinstallation or other attack vectors.

MitigationUpdate the plugin to version 3.2.9 or later when available; if no patch exists, disable the plugin immediately and implement web application firewall rules to block requests to the vulnerable 'delete-file' endpoint.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Verify Extensions For CF7 plugin is installed
    Inspect the WordPress plugins directory (wp-content/plugins/) for a folder named 'extensions-for-cf7' or similar. Alternatively, query the WordPress database table wp_options for option_name 'active_plugins' and check if the plugin appears in the serialized array.
    Affected if Plugin folder exists in wp-content/plugins/ or plugin is listed in active_plugins option
  2. Determine installed plugin version
    Open the main plugin file (typically extensions-for-cf7.php or index.php inside the plugin folder) and locate the version comment or the version defined in the plugin header. Compare this version number to the fixed version 3.2.9.
    Affected if Version string found is lower than 3.2.9 or version information is unavailable (indicating older release)
  3. Confirm plugin is active on the site
    Check WordPress admin panel under Plugins > Installed Plugins to verify the plugin status. If no admin access, query the wp_options table for the 'active_plugins' option and search for the plugin's main file path.
    Affected if Plugin appears as active in WordPress admin or plugin path is present in active_plugins option value
  4. Inspect HTTP access logs for vulnerable endpoint requests
    Review web server access logs (Apache, Nginx, or reverse proxy) for POST or GET requests containing 'delete-file' or 'delete_file' in the URI or request parameters. Example pattern: grep -i 'delete.*file' /var/log/apache2/access.log
    Affected if Recent or historical requests to delete-file functionality are present in logs, indicating the vulnerable endpoint is reachable

A user is affected if the Extensions For CF7 plugin is installed, active, and running a version prior to 3.2.9, exposing the delete-file functionality to unauthenticated path manipulation.

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 3.2.9 or later when available; if no patch exists, disable the plugin immediately and implement web application firewall rules to block requests to the vulnerable 'delete-file' endpoint.

Recommended fix Moderate confidence

Version 3.2.9 or later (check WordPress plugin repository for latest release)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'Extensions For CF7 (Contact form 7 Database, Conditional Fields and Redirection)'
  4. Check if the currently installed version is 3.2.8 or lower
  5. If vulnerable, click 'Update Now' to update to the latest version, which should be 3.2.9 or higher
  6. After updating, verify the new version number in the plugins list
  7. Test that form submissions can still be deleted by administrators (this is the intended function, but ensure it works correctly post-patch)

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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