Unauthenticated information disclosure via public error logs
Published Oct 11, 2025 · Updated Apr 8, 2026
Sensitive information exposure in Code Quality Control Tool 2.1 and earlier allows remote attackers to read PHP error logs over HTTP. The plugin's error_logger.php writes runtime errors to log files in a web-accessible location without preventing direct requests to those files. No authentication or user interaction is required; exposed entries can reveal application or environment data, while no write or availability impact is reported.
Summary
What happened
Sensitive information exposure in Code Quality Control Tool 2.1 and earlier allows remote attackers to read PHP error logs over HTTP. The plugin's error_logger.php writes runtime errors to log files in a web-accessible location without preventing direct requests to those files. No authentication or user interaction is required; exposed entries can reveal application or environment data, while no write or availability impact is reported.
The record
- CVE
- CVE-2025-8484
- Published
- Oct 11, 2025
- Updated
- Apr 8, 2026
- Vendor
- nickclarkweb
- Product
- Code Quality Control Tool
- Classifications
- CWE-200, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 11, 2025CVE publishedPublication date reported by the CVE source.
- Apr 8, 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.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