CVE-2026-29047
SQL Injection in GLPI Logs Export Allows Data Manipulation
Publication date: 2026-04-06
Last updated on: 2026-04-07
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| glpi-project | glpi | From 11.0.0 (inc) to 11.0.6 (exc) |
| glpi-project | glpi | From 10.0.0 (inc) to 10.0.24 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-29047 is a high-severity authenticated SQL injection vulnerability in the GLPI software package versions 10.0.0 to before 10.0.24 and 11.0.6. It occurs in the logs export feature, where an authenticated user can inject malicious SQL commands due to improper neutralization of special elements in SQL queries.
This happens because the software constructs SQL commands using user-controllable input without proper sanitization or escaping, allowing the injected SQL code to alter the intended query behavior.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows unauthorized access, modification, and potential disruption of the database, impacting confidentiality, integrity, and availability of data at a high level.
Such impacts can lead to non-compliance with common standards and regulations like GDPR and HIPAA, which require protection of sensitive data and maintaining data integrity and availability.
Therefore, if exploited, this vulnerability could result in violations of these regulations due to exposure or alteration of protected information.
How can this vulnerability impact me? :
This vulnerability can have a significant impact on confidentiality, integrity, and availability of the affected system.
- Confidentiality Impact: An attacker can gain unauthorized access to sensitive data in the database.
- Integrity Impact: An attacker can modify data in the database, potentially corrupting or altering important information.
- Availability Impact: The service can be disrupted, causing denial of service or other availability issues.
The vulnerability can be exploited remotely over the network by an authenticated user without requiring additional user interaction.
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to upgrade the GLPI software to the fixed versions 10.0.24 or 11.0.6, where the SQL injection issue in the logs export feature has been resolved.