dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-14345

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-07
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 7 weeks old

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 – Funnel Builder for WooCommerce with Checkout & One Click Upsell plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 3.12.7 via the 'postData' parameter parameter. This is due to unsanitized write of attacker-controlled postData values into a PHP-includeable .log file combined with the use of include_once to render that file in wpfnl_show_log. This makes it possible for unauthenticated attackers to execute code on the server. Exploitation requires that the Log Settings "Enable Logs" toggle is on and that an administrator subsequently opens the polluted log file via the plugin's Log Settings View UI; however, the nonce required to reach the optin endpoint is publicly emitted on every funnel step page, so the injection step itself is fully unauthenticated.

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 plugin allows unauthenticated attackers to inject PHP code into log files via the postData parameter, exploiting a nonce leaked on public funnel pages. When an administrator later views the log file through the plugin's Log Settings UI, the injected code executes via include_once. This is a log poisoning RCE requiring both the log feature to be enabled and admin interaction.

MitigationImmediately disable the 'Enable Logs' setting in plugin configuration. Apply vendor patch (3.12.8+) when available and audit server for any successful exploitation.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 installation and version
    Navigate to WordPress admin > Plugins > Installed Plugins and locate WPFunnels. Note the installed version number. Alternatively, check the plugin file at wp-content/plugins/wpfunnels/languages/wpfunnels.pot or readme.txt for the Version: field.
    Affected if The installed version is lower than 3.12.8 (the vendor patch version)
  2. Confirm whether logging is enabled in plugin settings
    Access the WPFunnels plugin settings UI, typically found under WPFunnels > Settings or Funnels > Settings. Locate the 'Enable Logs' or 'Logging' toggle/checkbox and note its current state.
    Affected if The 'Enable Logs' setting is currently ENABLED (this is required for the vulnerability to be exploitable)
  3. Inspect plugin log files for suspicious content
    Navigate to the WPFunnels log directory, commonly located in wp-content/uploads/wpfunnels/logs/ or wp-content/plugins/wpfunnels/logs/. Open the log files (typically named with dates or as funnel-logs.txt) and examine entries for PHP code patterns such as '<?php', 'eval(', 'base64_decode(', system commands, or unusual URL-encoded content in the postData fields.
    Affected if Log files contain unexpected PHP code, suspicious shell commands, or encoded payloads that were not intentionally logged by your workflows

You are affected if the WPFunnels plugin version is below 3.12.8 AND the 'Enable Logs' feature is enabled, as both conditions are required for this log poisoning RCE to be exploitable.

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

Immediately disable the 'Enable Logs' setting in plugin configuration. Apply vendor patch (3.12.8+) when available and audit server for any successful exploitation.

Recommended fix High confidence

WPFunnels plugin version 3.12.8 or later

  1. Update the WPFunnels plugin to version 3.12.8 or later through the WordPress admin dashboard (Plugins > Add New > Upload or directly via Plugins list > Update now)
  2. Verify the update was successful by checking the plugin version in Plugins list
  3. If logs are not needed in production, navigate to WPFunnels > Settings > Logs and disable the 'Enable Logs' toggle as an additional hardening measure
  4. Clear any existing .log files in the wp-content/uploads/wpfnl-logs/ directory that may have been created during attempted exploitation

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-2026-14345 — 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-2026-14345 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