CVE-2025-24799
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 unauthenticated user can perform a SQL injection through the inventory endpoint. This vulnerability is fixed in 10.0.18.
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 IT management software contains an unauthenticated SQL injection vulnerability in its inventory endpoint. An attacker can exploit this by sending malicious SQL queries through the inventory functionality without any authentication, potentially allowing full database compromise.
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.18CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 installed GLPI versionLocate the version file in your GLPI installation directory (typically version.php or similar) and read the version number, or access the GLPI web footer which displays the versionAffected if The version is 10.0.0 through 10.0.17 (any version >= 10.0.0 and < 10.0.18)
-
Confirm inventory functionality is activeCheck GLPI configuration files or web interface to determine if the inventory module (FusionInventory or native inventory) is enabled and runningAffected if Inventory functionality is enabled and the vulnerability can be triggered through it
-
Verify inventory endpoint accessibilityAttempt to access the inventory endpoint URL (commonly /plugins/fusioninventory/ or /ajax/inventory.php) from an unauthenticated perspective to confirm it is reachable without credentialsAffected if The inventory endpoint is exposed to unauthenticated network access
You are affected if your GLPI version is 10.0.0 to 10.0.17 AND the inventory module is enabled and accessible to unauthenticated users.
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.18
Upgrade GLPI to version 10.0.18 or later to patch the SQL injection vulnerability. If immediate upgrade is not possible, consider disabling or restricting access to the inventory endpoint as a temporary mitigation.
10.0.18
- 1. Backup your GLPI database and files before performing any upgrade
- 2. Download GLPI version 10.0.18 from the official GitHub repository or website
- 3. Extract the new version files to your web server document root
- 4. Copy your existing configuration file (config_db.php) from the old installation to the new one if not already present
- 5. Run the upgrade process by accessing GLPI in your browser - the system will automatically detect the old version and prompt for upgrade
- 6. Verify the upgrade was successful by logging in and checking the GLPI version number
- 7. Test the inventory endpoint functionality to confirm the SQL injection vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24799 — 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-2025-24799 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