Local file disclosure via uncontrolled PHP inclusion
Published Aug 20, 2025 · Updated May 13, 2026
Local file inclusion in FunnelKit Funnel Builder 3.11.1 and earlier allows remote attackers to expose local file contents. The public advisory identifies an uncontrolled PHP include or require filename but does not disclose the affected function, request parameter, or file path. Exploitation is unauthenticated but requires a privileged user to perform an action, and exposed files can include site credentials.
Summary
What happened
Local file inclusion in FunnelKit Funnel Builder 3.11.1 and earlier allows remote attackers to expose local file contents. The public advisory identifies an uncontrolled PHP include or require filename but does not disclose the affected function, request parameter, or file path. Exploitation is unauthenticated but requires a privileged user to perform an action, and exposed files can include site credentials.
The record
- CVE
- CVE-2025-54750
- Published
- Aug 20, 2025
- Updated
- May 13, 2026
- Vendor
- FunnelKit
- Product
- FunnelKit Funnel Builder
- Classifications
- CWE-98, CAPEC-252
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 20, 2025CVE publishedPublication date reported by the CVE source.
- May 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=3.11.1 changes=[{"at":"3.12.0","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo