dbcve.org
GlpiApplication · Glpi Project

CVE-2025-66417

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-15
Fix available
A fix is available. Upgrade to 11.0.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
GLPI is a free asset and IT management software package. From 11.0.0, < 11.0.3, an unauthenticated user can perform a SQL injection through the inventory endpoint. This vulnerability is fixed in 11.0.3.

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 confidence

Unauthenticated SQL injection vulnerability in GLPI versions 11.0.0 through 11.0.2 allows remote attackers to inject arbitrary SQL queries through the inventory endpoint. This critical flaw enables complete database compromise without any authentication credentials.

MitigationUpgrade GLPI to version 11.0.3 or later to patch the SQL injection vulnerability. If immediate upgrade is not possible, restrict network access to the inventory endpoint as an interim measure.

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
GlpiApplication
Affected:>= 11.0.0, < 11.0.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed GLPI version
    Locate the GLPI version file or access the version information through the GLPI front-end (typically found in the footer of the admin pages or in a version.php file within the GLPI installation directory). Compare this version number against the affected range: 11.0.0 through 11.0.2.
    Affected if The installed version is 11.0.0, 11.0.1, or 11.0.2.
  2. Verify the inventory endpoint exists and is enabled
    Check if the inventory functionality is active in the GLPI installation. This is typically found in the GLPI configuration settings under plugins or inventory settings, or by attempting to access the standard inventory API path (commonly /glpi/front/inventory.php or /api/inventory).
    Affected if The inventory endpoint is present and enabled in the GLPI instance.
  3. Confirm network accessibility to the inventory endpoint
    Determine if the inventory endpoint is reachable from untrusted networks. Test HTTP/HTTPS access to the inventory endpoint URL from an external host or verify firewall/network ACL rules that permit or restrict access to this endpoint.
    Affected if The inventory endpoint is accessible from networks where untrusted attackers could reach it without authentication.

The environment is affected if GLPI version is 11.0.0, 11.0.1, or 11.0.2 AND the inventory endpoint is enabled and accessible to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 11.0.3 or later
Fixed in 11.0.3
Interim mitigation

Upgrade GLPI to version 11.0.3 or later to patch the SQL injection vulnerability. If immediate upgrade is not possible, restrict network access to the inventory endpoint as an interim measure.

Recommended fix High confidence

11.0.3

  1. 1. Create a complete backup of the GLPI database and filesystems
  2. 2. Download GLPI version 11.0.3 from the official GitHub releases (github.com/glpi-project/glpi)
  3. 3. Extract the 11.0.3 release package to a temporary location
  4. 4. Replace the existing GLPI files with the new version 11.0.3 files, or use the built-in upgrade functionality if available
  5. 5. Verify file permissions are correctly set after the upgrade
  6. 6. Clear any application caches if applicable
  7. 7. Test the inventory endpoint functionality to confirm the fix works and the application functions normally
Caveat Review GLPI 11.0.3 release notes for any compatibility notes or migration requirements before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Glpi Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,370
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,192.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-66417 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-66417 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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