Unauthenticated information disclosure via public debug logs
Published Apr 24, 2024 · Updated Apr 28, 2026
Information exposure in Simply Static 3.1.3 and earlier allows remote attackers to read sensitive data from public debug logs. Version 3.1.3 places the debug log in the web-served uploads directory, while the 3.1.4 security change adds a dynamic filename and an .htaccess access rule. No authentication or user interaction is required; exposure is limited to data written into the log, with no reported modification or service interruption.
Summary
What happened
Information exposure in Simply Static 3.1.3 and earlier allows remote attackers to read sensitive data from public debug logs. Version 3.1.3 places the debug log in the web-served uploads directory, while the 3.1.4 security change adds a dynamic filename and an .htaccess access rule. No authentication or user interaction is required; exposure is limited to data written into the log, with no reported modification or service interruption.
The record
- CVE
- CVE-2024-32825
- Published
- Apr 24, 2024
- Updated
- Apr 28, 2026
- Vendor
- Simply Static
- Product
- Simply Static
- Classifications
- CWE-201
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 24, 2024CVE 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 <=3.1.3 changes=[{"at":"3.1.4","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