Account takeover via non-string API token query
Published Sep 14, 2022 · Updated Apr 23, 2025
SQL injection in GLPI 9.1 through 10.0.2 allows remote attackers to assume any account that has an API token configured. The external-token authentication path passes a caller-controlled token to User::getFromDBbyToken(), which accepted a query-condition array such as REGEX .* instead of requiring a scalar string. Exploitation requires external-token login to be enabled and at least one defined API token; success grants the matched user's session.
Summary
What happened
SQL injection in GLPI 9.1 through 10.0.2 allows remote attackers to assume any account that has an API token configured. The external-token authentication path passes a caller-controlled token to User::getFromDBbyToken(), which accepted a query-condition array such as REGEX .* instead of requiring a scalar string. Exploitation requires external-token login to be enabled and at least one defined API token; success grants the matched user's session.
The record
- CVE
- CVE-2022-35947
- Published
- Sep 14, 2022
- Updated
- Apr 23, 2025
- Vendor
- GLPI Project
- Product
- GLPI
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 14, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 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=>= 9.1, < 10.0.3
What conditions does exploitation require?
What is affected?
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