Information disclosure via detailed status output
Published Feb 25, 2025 · Updated Feb 25, 2025
Information disclosure in GLPI 0.71 through 10.0.17 allows remote attackers to read configured service names via status.php. The unauthenticated endpoint invokes StatusChecker::getServiceStatus with detailed output enabled and serializes active LDAP directory, mail authentication provider, and mail receiver names into its response. No account or user interaction is required; exposure is limited to values stored in those name fields, which can contain sensitive information.
Summary
What happened
Information disclosure in GLPI 0.71 through 10.0.17 allows remote attackers to read configured service names via status.php. The unauthenticated endpoint invokes StatusChecker::getServiceStatus with detailed output enabled and serializes active LDAP directory, mail authentication provider, and mail receiver names into its response. No account or user interaction is required; exposure is limited to values stored in those name fields, which can contain sensitive information.
The record
- CVE
- CVE-2025-21626
- Published
- Feb 25, 2025
- Updated
- Feb 25, 2025
- Vendor
- GLPI Project
- Product
- GLPI
- Classifications
- CWE-200, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 25, 2025CVE publishedPublication date reported by the CVE source.
- Feb 25, 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=>= 0.71, < 10.0.18
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