CVE-2024-40638
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. An authenticated user can exploit multiple SQL injection vulnerabilities. One of them can be used to alter another user account data and take control of it. Upgrade to 10.0.17.
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 contains multiple SQL injection vulnerabilities exploitable by authenticated users. At least one vulnerability allows attackers to modify another user's account data, potentially leading to complete account takeover.
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>= 0.85, < 10.0.17CVSS 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 versionLocate the version file typically at 'inc/product_infos.php' or check the version displayed in the GLPI login page footer, or query the database table 'glpi_configs' for 'version' entryAffected if version is >= 0.85 and < 10.0.17
-
Confirm GLPI is runningAccess the GLPI web interface via HTTP/HTTPS and verify the login page loadsAffected if GLPI is accessible and responds with the GLPI login page
-
Verify user authentication is enabledCheck that the GLPI authentication system is active by attempting to log in or checking 'auth' tables in the databaseAffected if authenticated user sessions can be created in the GLPI application
You are affected if your GLPI installation version is 0.85 or higher but lower than 10.0.17, and the web application with user authentication is accessible to attackers.
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.17
Upgrade GLPI to version 10.0.17 or later to remediate the SQL injection vulnerabilities.
10.0.17
- 1. Create a complete backup of the GLPI database and all application files
- 2. Download GLPI version 10.0.17 from the official GitHub releases page (github.com/glpi-project/glpi) or the official GLPI website
- 3. Follow the official GLPI upgrade procedure: disable maintenance mode if enabled, extract the new version files over the existing installation, run the migration scripts via the web interface or CLI
- 4. Clear any cached data (var/cache directory)
- 5. Verify the upgrade was successful by logging in and checking the version number in Help > About
- 6. Test that SQL injection is no longer reproducible
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-40638 — 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-2024-40638 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