Unauthenticated log disclosure via predictable filename
Published Jun 3, 2024 · Updated Apr 28, 2026
Sensitive data exposure in Debug Log Manager Tool 1.4.5 and earlier allows remote attackers to read WordPress debug log contents. The plugin enables WordPress logging at a predictable debug.log path instead of assigning the randomized log filename introduced by the security fix. Exploitation requires WordPress debugging and file logging to be enabled; exposed entries can reveal application errors and other data written to the log.
Summary
What happened
Sensitive data exposure in Debug Log Manager Tool 1.4.5 and earlier allows remote attackers to read WordPress debug log contents. The plugin enables WordPress logging at a predictable debug.log path instead of assigning the randomized log filename introduced by the security fix. Exploitation requires WordPress debugging and file logging to be enabled; exposed entries can reveal application errors and other data written to the log.
The record
- CVE
- CVE-2024-34798
- Published
- Jun 3, 2024
- Updated
- Apr 28, 2026
- Vendor
- Lukman Hussain Nakib
- Product
- Debug Log Manager Tool
- Classifications
- CWE-532, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 3, 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 <=1.4.5 changes=[{"at":"1.5","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