Unauthenticated debug data disclosure via predictable log filename
Published Jan 5, 2024 · Updated Apr 28, 2026
Sensitive information exposure in Aaron J 404 Solution 2.33.0 and earlier allows remote attackers to read debug log data. The getDebugFilePath logic stores the debug log under a predictable fixed filename in a web-accessible uploads directory rather than assigning an unpredictable name. No authentication or user interaction is required; exposed content can include plugin configuration and diagnostic data.
Summary
What happened
Sensitive information exposure in Aaron J 404 Solution 2.33.0 and earlier allows remote attackers to read debug log data. The getDebugFilePath logic stores the debug log under a predictable fixed filename in a web-accessible uploads directory rather than assigning an unpredictable name. No authentication or user interaction is required; exposed content can include plugin configuration and diagnostic data.
The record
- CVE
- CVE-2023-52146
- Published
- Jan 5, 2024
- Updated
- Apr 28, 2026
- Vendor
- AJ Experience
- Product
- 404 Solution
- Classifications
- CWE-532, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 5, 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=n/a <=2.33.0 changes=[{"at":"2.33.1","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
- TsukuCTF 2025 404 Solution log-disclosure write-upproof of concept · demonstrated
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