CVE-2025-54750
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 · uneditedImproper 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.11.1.
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 confidenceA Local File Inclusion (LFI) vulnerability in the Funnel Builder by FunnelKit WordPress plugin allows unauthenticated attackers to manipulate PHP include/require statements by controlling the filename parameter, potentially leading to arbitrary code execution if malicious PHP files can be uploaded to the server.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Funnel Builder by FunnelKit is installedNavigate to WordPress admin dashboard > Plugins, or inspect the /wp-content/plugins/funnel-builder directory via file system or FTPAffected if The Funnel Builder by FunnelKit plugin appears in the installed plugins list
-
Identify the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins > Funnel Builder by FunnelKit and read the version number displayed below the plugin name; alternatively, check the main plugin PHP file header in /wp-content/plugins/funnel-builder/Affected if The installed version is older than the patched version released for this CVE
-
Verify the vulnerable filename parameter is accessibleInspect the plugin source code for files handling the filename parameter in include/require statements; search for patterns like $_GET['filename'] or $_REQUEST['filename'] used in include, require, include_once, or require_once functionsAffected if Code exists that uses a user-controlled filename parameter in PHP include/require functions without proper sanitization
-
Check if PHP allows remote file inclusionReview the PHP configuration file (php.ini) for the allow_url_fopen and allow_url_include settings; also check for disabled_functions restrictionsAffected if allow_url_fopen is enabled and no restrictions exist on file inclusion functions, making exploitation more feasible
Your environment is affected if the Funnel Builder by FunnelKit plugin is installed with a version prior to the patched release and contains vulnerable code handling the filename parameter in PHP include statements.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to the latest version of Funnel Builder by FunnelKit immediately. If no patched version is available, disable the plugin and implement a Web Application Firewall (WAF) rule to block directory traversal patterns in query parameters.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54750 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-54750 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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