GLPI · weakness class
SQL Injection
48 CVEs
Every dot is a CVE in what this vendor ships; the named ones are the most at risk.
- check available
- 3
- likely to be exploited
- 11
Every one of the 48 is a mark on the map. Named now: 1 to 26, most at risk first.
- GLPI < 10.0.17 - Pre-Auth SQL Injection
- GLPI 10.0.10-10.0.14 - SQL Injection
- GLPI - Blind SQL Injection in History Log Filter (LogBleed)
- GLPI SQL injection through inventory agent request
- GLPI contains an authenticated SQL injection
- SQL Injection in through the search engine
- GLPI vulnerable to SQL injection via inventory agent request
- SQL injection on login page in GLPI
- GLPI vulnerable to SQL injection through Computer Virtual Machine information
- GLPI allows account takeover via SQL Injection in AJAX scripts
- SQL Injection on REST API in GLPI
- Account takeover via SQL Injection in UI layout preferences in GLPI
- glpi Authenticated SQL Injection
- GLPI allows account takeover via SQL Injection in AJAX scripts
- SQL injection with _actor parameter in GLPI
- GLPI has an Unauthenticated SQL Injection via Search engine
- GLPI Inventory Plugin is Vulnerable to Unauthenticated SQL Injection
- SQL injection vulnerability in ajax/getDropdownValue.php in GLPI before 0.85.1 allows remote authenticated users to execute arbitrary SQL commands via the condition parameter.
- Multiple SQL injection vulnerabilities in GLPI before 0.83.9 allow remote attackers to execute arbitrary SQL commands via the (1) users_id_assign parameter to ajax/ticketassigninf…
- A SQL Injection vulnerability exits in the Ramo plugin for GLPI 9.4.6 via the idu parameter in plugins/ramo/ramoapirest.php/getOutdated.
- SQL injection exists in front/devicesoundcard.php in GLPI before 9.1.5 via the start parameter.
- GLPI before 9.1.5.1 has SQL Injection in the $crit variable in inc/computer_softwareversion.class.php, exploitable via ajax/common.tabs.php.
- Multiple SQL injection vulnerabilities in GLPI 0.90.4 allow an authenticated remote attacker to execute arbitrary SQL commands by using a certain character when the database is co…
- GLPI before 9.1.5.1 has SQL Injection in the condition rule field, exploitable via front/rulesengine.test.php.
- GLPI before 9.1.5 allows SQL injection via an ajax/getDropdownValue.php request with an entity_restrict parameter that is not a list of integers.
- SQL Injection in glpi
exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it
Zoom in on the map and the dots under the middle of it are named where they are.
Data as of 2026-11-15. CVE List through 2026-11-15 · EPSS of 2026-11-14 · CISA KEV checked 2026-11-15. Sources: the CVE List, CISA KEV, EPSS, NVD, nuclei templates and public bug bounty data.