dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2026-13080

MEDIUM · 6.6 CVSS v3.1 Published 2026-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 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 Local File Inclusion in all versions up to, and including, 3.12.7 via the 'logKey' parameter parameter. This makes it possible for authenticated attackers, with administrator-level access and above, to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included.

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 for WordPress contains a Local File Inclusion (LFI) vulnerability in all versions up to 3.12.7. The vulnerability exists via the 'logKey' parameter, allowing authenticated attackers with administrator-level permissions to include and execute arbitrary .php files on the server, leading to arbitrary PHP code execution.

MitigationUpdate the WPFunnels plugin to version 3.12.8 or later to remediate this vulnerability. If an update is unavailable, consider disabling the plugin or implementing web application firewall rules to block directory traversal attempts in the 'logKey' parameter.

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
High
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:H/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 is installed
    Log into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for WPFunnels in the list. Alternatively, check the file system at /wp-content/plugins/ for a wpfunnels directory.
    Affected if WPFunnels plugin directory exists in the WordPress installation
  2. Check installed WPFunnels version
    In WordPress admin, go to Plugins > Installed Plugins > WPFunnels and view the version number displayed. Or read the main plugin file (e.g., wpfunnels.php) and look for the 'Version' header in the plugin comments.
    Affected if Installed version is 3.12.7 or lower (any version up to and including 3.12.7)
  3. Confirm administrator-level access exists
    Review WordPress user roles at Users > All Users. Verify if any user accounts have the Administrator role, as this CVE requires administrator-level permissions to exploit.
    Affected if At least one user account with Administrator role exists on the WordPress site
  4. Identify vulnerable endpoint exposure
    Examine web server logs or traffic for requests to WPFunnels endpoints containing the 'logKey' parameter. Common paths may include ajax handlers or specific funnel-related routes within the plugin.
    Affected if HTTP requests to WPFunnels endpoints with 'logKey' parameter are present in logs or accessible

The environment is affected if WPFunnels plugin version 3.12.7 or lower is installed on WordPress and the site has administrator-level user accounts, making the LFI via 'logKey' parameter 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

Update the WPFunnels plugin to version 3.12.8 or later to remediate this vulnerability. If an update is unavailable, consider disabling the plugin or implementing web application firewall rules to block directory traversal attempts in the 'logKey' parameter.

Recommended fix Moderate confidence

WPFunnels version 3.12.8 or later

  1. Log in to the WordPress admin dashboard with administrator privileges
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'WPFunnels – Funnel Builder for WooCommerce with Checkout & One Click Upsell' in the plugin list
  4. Check the current version number displayed under the plugin name
  5. If the installed version is 3.12.7 or earlier, click 'Update now' if an update is available
  6. Alternatively, download the latest version of WPFunnels from the official WordPress plugin repository (version 3.12.8 or later)
  7. Deactivate and delete the old version, then upload and install the new version
  8. After updating, verify the plugin is functioning correctly and test the affected functionality
Caveat Review the plugin's changelog before updating to check for any breaking changes or feature modifications that may affect your funnels

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
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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