CVE-2026-29047
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGLPI is a free asset and IT management software package. From 10.0.0 to before 10.0.24 and 11.0.6, an authenticated user can perform a SQL injection via the logs export feature. This vulnerability is fixed in 10.0.24 and 11.0.6.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGLPI asset management software versions 10.0.0 through 10.0.23 and 11.0.0 through 11.0.5 contain an authenticated SQL injection vulnerability in the logs export feature. An attacker with valid user credentials can inject malicious SQL statements through insufficiently sanitized input parameters in the export functionality, potentially allowing data exfiltration, manipulation, or unauthorized database access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 10.0.0, < 10.0.24>= 11.0.0, < 11.0.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify GLPI installation and versionLocate the GLPI installation directory and check the version.php or config file, typically in the root directory or /inc/ folder. Common paths include: check version.php, composer.json, or the GLPI dashboard under Setup > General > System information.Affected if Installed version is 10.0.0-10.0.23 or 11.0.0-11.0.5
-
Verify logs export feature is accessibleCheck if the logs export functionality is enabled in the GLPI configuration. Navigate to Administration > Logs or check config_export.php and related export settings in the GLPI database config table.Affected if The logs export feature is enabled and accessible to authenticated users
-
Confirm user authentication is requiredReview GLPI user management settings and session configuration to confirm that valid credentials are needed to access the logs export feature.Affected if The logs export is accessible to any authenticated user, not restricted to highly privileged administrators only
-
Inspect export-related code for input handlingExamine the PHP files handling logs export functionality, typically in ajax/export.php, front/export.php, or similar paths within the /ajax/ or /front/ directories. Look for direct use of user-supplied parameters in SQL queries without proper parameterization.Affected if The code uses raw $_GET, $_POST, or $_REQUEST parameters directly in SQL queries without sanitization
-
Check for unusual database query patternsReview GLPI web server access logs and database query logs for suspicious SQL patterns in export-related requests, such as UNION SELECT, OR 1=1, or other SQL injection payloads targeting export endpoints.Affected if Logs show SQL injection patterns in requests to export functionality from any authenticated user account
A user is affected if they run GLPI versions 10.0.0-10.0.23 or 11.0.0-11.0.5 AND have the logs export feature accessible to authenticated users without additional access restrictions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.0.2411.0.6
Upgrade GLPI to version 10.0.24 or 11.0.6 or later. If immediate upgrading is not feasible, restrict access to the logs export functionality to trusted administrative users only and implement web application firewall rules to detect and block SQL injection patterns.
GLPI 10.0.24 (for 10.0.x users) or GLPI 11.0.6 (for 11.0.x users)
- 1. Back up your GLPI database and files before upgrading
- 2. Identify your current GLPI version (check the version in the footer of the GLPI interface or in the config directory)
- 3. If you are on GLPI 10.0.x (version 10.0.0 through 10.0.23), download GLPI version 10.0.24
- 4. If you are on GLPI 11.0.x (version 11.0.0 through 11.0.5), download GLPI version 11.0.6
- 5. Follow the standard GLPI upgrade procedure: extract the new version files, copy the config directory from the old installation if needed, and ensure file permissions are correct
- 6. Clear any caching systems (like opcache) if applicable
- 7. Verify the upgrade was successful by logging in and checking the version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-29047 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-29047 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data