Unauthenticated PHP execution via local file inclusion
Published Apr 24, 2025 · Updated Apr 28, 2026
Local file inclusion in Capturly Capturly 2.0.1 and earlier allows remote attackers to execute server-side PHP through local files. Patchstack has not published the vulnerable endpoint, parameter, or include/require call that accepts an attacker-influenced filename. Exploitation requires no account but does require user interaction according to the CNA vector; successful inclusion can expose files or execute PHP code already present on the server.
Summary
What happened
Local file inclusion in Capturly Capturly 2.0.1 and earlier allows remote attackers to execute server-side PHP through local files. Patchstack has not published the vulnerable endpoint, parameter, or include/require call that accepts an attacker-influenced filename. Exploitation requires no account but does require user interaction according to the CNA vector; successful inclusion can expose files or execute PHP code already present on the server.
The record
- CVE
- CVE-2025-39379
- Published
- Apr 24, 2025
- Updated
- Apr 28, 2026
- Vendor
- Capturly
- Product
- Capturly
- Classifications
- CWE-98, CAPEC-252, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 24, 2025CVE publishedPublication date reported by the CVE source.
- Apr 28, 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 <=2.0.1 changes=[{"at":"2.0.2","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