GLPi-project GLPI any version

SQL injection in GLPI

GLPI vulnerable to unallowed PHP script execution

GLPI vulnerable to SQL injection and Stored XSS via inventory agent request

/vendor/htmlawed/htmlawed/htmLawedTest.php in the htmlawed module for GLPI through 10.0.2 allows PHP code injection.

GLPI allows unauthenticated SQL injection through the inventory endpoint

GLPI SQL injection through inventory agent request

SQL injection on login page in GLPI

GLPI vulnerable to SQL injection via inventory agent request

GLPI vulnerable to SQL injection through Computer Virtual Machine information

SQL Injection on REST API in GLPI

Account takeover via SQL Injection in UI layout preferences in GLPI

SQL injection with _actor parameter in GLPI

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.

GLPI Remote code execution from LDAP server configuration form on PHP 7.4

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 ITIL actors in GLPI

GLPI has an unauthenticated SQL injection through the inventory endpoint

GLPI allows SQL injection through the rules configuration

GLPI has an Unauthenticated SQL Injection via Search engine

Blind Server-Side Request Forgery (SSRF) using Arbitrary Object Instantiation in GLPI

GLPI vulnerable to SQL injection through dynamic reports

GLPI vulnerable to unauthenticated session hijacking

weak CSRF tokens in GLPI

Unauthenticated File Deletion in GLPI

File deletion through document upload process in GLPI

GLPI vulnerable to SQL injection via dashboard administration

GLPI has a Server-Side Template Injection via Double-Compilation

GLPI is Vulnerable to SSRF via Webhooks

Remote Code Execution in GLPI

Unrestricted file upload in GLPI before 0.85.3 allows remote authenticated users to execute arbitrary code by adding a file with an executable extension as an attachment to a new ticket, then accessing it via a direct request to the file in files/_tmp/.

GLPI allows account takeover via SQL Injection in AJAX scripts

Account takeover via Kanban feature in GLPI

glpi Authenticated SQL Injection

GLPI allows remote code execution through the plugin loader

GLPI allows authenticated remote code execution

GLPI through 9.4.3 is prone to account takeover by abusing the ajax/autocompletion.php autocompletion feature. The lack of correct validation leads to recovery of the token generated via the password reset functionality, and thus an authenticated attacker can set an arbitrary password for any user. This vulnerability can be exploited to take control of admin account. This vulnerability could be also abused to obtain other sensitive fields like API keys or password hashes.

The constructSQL function in inc/search.class.php in GLPI 9.2.x through 9.3.0 allows SQL Injection, as demonstrated by triggering a crafted LIMIT clause to front/computer.php.

GLPI before 9.1.5.1 has SQL Injection in the condition rule field, exploitable via front/rulesengine.test.php.

IP restriction on GLPI API Bypass with custom header injection