dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-12000

MEDIUM · 6.5 CVSS v3.1 Published 2025-11-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 WPFunnels plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the wpfnl_delete_log() function in all versions up to, and including, 3.6.2. This makes it possible for authenticated attackers, with Administrator-level access and above, 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 WPFunnels WordPress plugin has an arbitrary file deletion vulnerability in the wpfnl_delete_log() function due to insufficient file path validation. Authenticated administrators can manipulate the file path parameter to delete any file on the server, such as wp-config.php, enabling remote code execution.

MitigationUpdate WPFunnels to version 3.6.3 or later. Until patched, restrict administrator access and monitor for suspicious delete 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
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Verify WPFunnels plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for WPFunnels, or check the /wp-content/plugins/ directory for the wpfunnels folder
    Affected if WPFunnels plugin is present in the WordPress installation
  2. Determine installed WPFunnels version
    In WordPress admin, go to Plugins > Installed Plugins > WPFunnels and note the version number displayed, or read the main plugin file header in /wp-content/plugins/wpfunnels/wpfunnels.php
    Affected if The installed version is older than the patched release (compare your version to the fixed release noted in security advisories)
  3. Confirm administrator-level access exists
    In WordPress admin, go to Users and review user roles; the vulnerability requires an administrator-level account to exploit
    Affected if Any user with Administrator role exists in the WordPress installation
  4. Check if logging feature is active
    Examine the WPFunnels plugin settings in the WordPress admin panel for any logging or log management features that invoke the wpfnl_delete_log function
    Affected if Logging functionality that uses the vulnerable delete function is enabled or accessible
  5. Verify wp-config.php integrity
    Confirm that /wp-config.php exists and has not been recently modified or deleted; check file modification timestamp and compare hash if possible
    Affected if wp-config.php is missing or shows unexpected recent modifications indicating potential deletion or tampering

Your environment is affected if WPFunnels plugin is installed with a version prior to the patched release and you have administrator accounts that could trigger the vulnerable wpfnl_delete_log function.

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 WPFunnels to version 3.6.3 or later. Until patched, restrict administrator access and monitor for suspicious delete requests.

Recommended fix Moderate confidence

WPFunnels version 3.6.3 or later

  1. 1. Check your current WPFunnels plugin version in WordPress admin under Plugins > Installed Plugins
  2. 2. If the installed version is 3.6.2 or below, navigate to Dashboard > Updates or Plugins > Add New > Upload Plugin
  3. 3. Update WPFunnels to the latest available version (version 3.6.3 or later, which contains the fix for CVE-2025-12000)
  4. 4. Verify the update completed successfully and the plugin is functioning normally
  5. 5. Confirm the wp-config.php file still exists and your site is accessible
Caveat Review plugin changelog for any breaking changes between your current version and the update version before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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