Diagnostic information disclosure via unresolved Database class
Published Jan 29, 2023 · Updated Mar 28, 2025
Unchecked error handling in Froxlor before 2.0.10 allows remote attackers to obtain low-sensitivity diagnostic information. The error-report path calls Database::getAttribute without importing Froxlor\Database\Database, so PHP resolves an undefined class outside the Exception handler. A reachable report with a valid error identifier exposes stored SQL error details and a stack trace; no data modification or service interruption is reported.
Summary
What happened
Unchecked error handling in Froxlor before 2.0.10 allows remote attackers to obtain low-sensitivity diagnostic information. The error-report path calls Database::getAttribute without importing Froxlor\Database\Database, so PHP resolves an undefined class outside the Exception handler. A reachable report with a valid error identifier exposes stored SQL error details and a stack trace; no data modification or service interruption is reported.
The record
- CVE
- CVE-2023-0572
- Published
- Jan 29, 2023
- Updated
- Mar 28, 2025
- Vendor
- Froxlor
- Product
- Froxlor
- Classifications
- CWE-754, CWE-391, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 29, 2023CVE publishedPublication date reported by the CVE source.
- Mar 28, 2025Record 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=unspecified <2.0.10
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