CVE-2025-66417 is a high severity SQL injection (CVSS 7.5) in GLPI, the open source IT asset management tool. From 11.0.0 up to but not including 11.0.3, an unauthenticated user can inject SQL through the inventory endpoint. Upgrade to GLPI 11.0.3 or later.
What's affected
- GLPI from 11.0.0 and before 11.0.3.
- Fixed version: 11.0.3.
- GLPI 10.x is outside the range stated in the advisory.
How to check if you're exposed
Sign in as an administrator and read the version in the footer or on the setup page. On the server, the version is also in the application files. For a container deployment, check the image tag you run.
Any 11.0.0, 11.0.1 or 11.0.2 install is in range. Review your web server logs for unexpected requests to the inventory endpoint from addresses that are not your agents, since the weakness is reachable without a login.
What to do now
- Back up the GLPI database and files.
- Upgrade to GLPI 11.0.3 or later, following the project's upgrade guide.
- If you cannot upgrade today, restrict the inventory endpoint to the networks your inventory agents use.
- Review web and database logs for unusual requests to that endpoint.
- Rotate credentials stored in GLPI if you find signs of misuse.
Why it matters
The weakness is CWE-89, SQL injection. Input that should be treated as data reaches a database query as part of the command, so a caller can change what the query does.
The vector scores high for confidentiality only, which matches data being read out of the database rather than changed. An asset management database often holds user names, device details and internal addresses. The record does not list this CVE as exploited in the wild.
A few practices limit the damage from any injection flaw in an internal tool. Run the database account that GLPI uses with only the rights it needs, keep the database on a host that accepts connections only from the application server, and keep recent backups that you have tested.
For a tool like GLPI, inventory endpoints exist so agents can report in, which means they must be reachable from many machines. That is a reason to restrict them by network, so that only your agent subnets can call them, instead of leaving them open to everyone who can reach the web server.
Finally, use this advisory to check how quickly you can patch an internal application. If upgrading GLPI takes weeks of coordination, that delay is the risk to fix next.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Does an attacker need a GLPI account for CVE-2025-66417?
No. The advisory describes an unauthenticated user reaching the inventory endpoint. Fixed in 11.0.3.
Sources
Last reviewed: 19 October 2026.
