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

CVE-2025-26979

HIGH · 7.5 CVSS v3.1 Published 2025-02-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Aman Funnel Builder by FunnelKit funnel-builder allows PHP Local File Inclusion.This issue affects Funnel Builder by FunnelKit: from n/a through <= 3.9.0.

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 · moderate confidence

This is a PHP Local File Inclusion (LFI) vulnerability in the Funnel Builder by FunnelKit WordPress plugin. The vulnerability stems from improper validation of user-supplied input used in PHP include/require statements, allowing attackers to include arbitrary local files. This can lead to sensitive data exposure or remote code execution if attacker-controlled files can be placed on the system.

MitigationUpdate Funnel Builder to the latest version if available, or apply input validation/sanitization to all file inclusion operations to restrict included files to expected paths. Consider deploying a WAF rule to block directory traversal patterns until a patch is applied.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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. Confirm Funnel Builder plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for folders named 'funnel-builder' or 'funnelkit', or view the installed plugins list in WordPress admin under Plugins > Installed Plugins
    Affected if The Funnel Builder by FunnelKit plugin is present in the WordPress installation
  2. Identify the installed plugin version
    Open the main plugin PHP file (typically funnel-builder.php or funnels.php in the plugin root) and locate the 'Version:' header comment, or check the plugin row in WordPress admin plugins list which displays the version number
    Affected if The installed version is at or below the vulnerable version range (consult NVD or FunnelKit advisories for the exact affected version numbers)
  3. Locate file inclusion code paths
    Search the plugin directory for PHP include/require statements that use variables or request parameters (grep for 'include($', 'require($', 'include_once($', 'require_once($' combined with '$_GET', '$_POST', or '$_REQUEST')
    Affected if The plugin contains dynamic file inclusion operations using unsanitized user input without proper path validation
  4. Verify the vulnerable parameter is accessible
    Identify which query parameters feed into the file inclusion function (common names include 'file', 'path', 'template', 'page', 'view', or 'slug') and confirm whether the endpoint requires authentication or can be accessed anonymously
    Affected if The file inclusion parameter can be reached without authentication or with low-privilege user access, allowing remote attackers to supply malicious file paths
  5. Check for directory traversal patterns in recent access logs
    Review web server access logs (Apache/nginx error and access logs) for requests to the plugin's file inclusion endpoints containing '../' sequences or absolute paths like '/etc/passwd' targeting the Funnel Builder plugin
    Affected if Exploitation attempts or suspicious patterns matching LFI probes are found in logs associated with Funnel Builder plugin endpoints

A user is affected if the Funnel Builder by FunnelKit plugin is installed with a version containing the LFI vulnerability AND the vulnerable file inclusion endpoint is accessible to attackers (typically without authentication).

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Funnel Builder to the latest version if available, or apply input validation/sanitization to all file inclusion operations to restrict included files to expected paths. Consider deploying a WAF rule to block directory traversal patterns until a patch is applied.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.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-26979 — 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-26979 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