Unauthenticated local file inclusion
Published Apr 24, 2025 · Updated May 12, 2026
Local file inclusion in CodeWorkWeb CWW Portfolio 1.3.1 and earlier allows remote attackers to include local server files. Patchstack does not disclose the affected PHP file, request parameter, or include operation. No authentication is required, but exploitation requires a privileged user to interact with attacker-supplied content; included file output can expose local data.
Summary
What happened
Local file inclusion in CodeWorkWeb CWW Portfolio 1.3.1 and earlier allows remote attackers to include local server files. Patchstack does not disclose the affected PHP file, request parameter, or include operation. No authentication is required, but exploitation requires a privileged user to interact with attacker-supplied content; included file output can expose local data.
The record
- CVE
- CVE-2025-39359
- Published
- Apr 24, 2025
- Updated
- May 12, 2026
- Vendor
- CodeWorkWeb
- Product
- CWW Portfolio
- Classifications
- CWE-98, CAPEC-193, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 24, 2025CVE publishedPublication date reported by the CVE source.
- May 12, 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 <=1.3.1
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