CVE-2026-53629 GLPI: SQL injection in history tab
An attacker with log read access can inject SQL via the history tab URL, allowing unauthorized database access in GLPI.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-53629?
CVE-2026-53629 is a high-severity SQL injection vulnerability in glpi-project glpi, published on 25 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
GLPI is a free asset and IT management software package. From 9.4.0 until 10.0.26 and 11.0.8, an attacker with the READ right on logs can craft a URL for the history tab that injects attacker-controlled values into a database query. This permits SQL injection through the history tab endpoint. This issue is fixed in versions 11.0.8 and 10.0.26.
Weakness: CWE-89
Which versions are affected by CVE-2026-53629?
How do I fix CVE-2026-53629?
No fix has been published for CVE-2026-53629 yet. Limit exposure of the affected software until one is available.
Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.
Is CVE-2026-53629 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53629 exists.
Public exploit code: 1 Nuclei template and 1 proofs of concept on GitHub.
Sources
Also known as GHSA-cpcj-x335-5cmh, UBUNTU-CVE-2026-53629.