dbcve.org
Glpi InventoryApplication · Glpi Project

CVE-2026-26001

HIGH · 8.8 CVSS v3.1 Published 2026-03-18
Fix available
A fix is available. Upgrade to 1.6.6 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
The GLPI Inventory Plugin handles network discovery, inventory, software deployment, and data collection for GLPI agents. Prior to 1.6.6, non sanitized user input can lend to an SQL injection from reports, with adequate rights. This vulnerability is fixed in 1.6.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 confidence

The GLPI Inventory Plugin versions prior to 1.6.6 contain an SQL injection vulnerability in the reports functionality. The vulnerability stems from insufficient sanitization of user input, allowing authenticated users with adequate rights to inject malicious SQL queries.

MitigationUpgrade the GLPI Inventory Plugin to version 1.6.6 or later. Until the upgrade is applied, restrict access to the reports functionality to only trusted, fully authenticated administrators.

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
Glpi InventoryApplication
Affected:< 1.6.6

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

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

  1. Locate GLPI Inventory Plugin installation
    Identify the directory where the glpi-inventory plugin is installed on the web server. This is typically found in the glpi/plugins/ directory.
    Affected if The plugin directory exists but version cannot be determined or is below 1.6.6
  2. Determine installed plugin version
    Check the version file or header within the glpi-inventory plugin directory. Common locations include a version.php file or plugin.xml in the plugin root.
    Affected if The installed version is any version prior to 1.6.6
  3. Verify reports functionality exists
    Confirm the reports module is present in the plugin by examining the plugin structure for report-related files or controllers.
    Affected if The reports functionality module exists in the installation
  4. Check access controls on reports
    Review user permissions and role assignments within GLPI to determine which authenticated users can access the reports feature.
    Affected if Users other than trusted administrators have access to the reports functionality
  5. Confirm plugin is in use
    Verify the glpi-inventory plugin is actively enabled and running on the GLPI instance by checking the plugin status in the GLPI administration panel.
    Affected if The plugin is enabled and running with a version below 1.6.6

The environment is affected if the GLPI Inventory Plugin is installed and enabled with a version prior to 1.6.6, and the reports functionality is accessible to authenticated 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 1.6.6 or later
Fixed in 1.6.6
Interim mitigation

Upgrade the GLPI Inventory Plugin to version 1.6.6 or later. Until the upgrade is applied, restrict access to the reports functionality to only trusted, fully authenticated administrators.

Recommended fix High confidence

1.6.6

  1. Backup your GLPI database and files before performing any upgrade
  2. Download GLPI Inventory Plugin version 1.6.6 from the official GLPI repository (github.com/GLPI-Project/glpi-inventory)
  3. Extract the new plugin files to the /glpi/plugins/ directory, replacing the existing glpi-inventory folder
  4. Log in to GLPI as an administrator
  5. Navigate to Setup > Plugins
  6. Find GLPI Inventory in the plugin list and click to upgrade/activate it
  7. Verify the plugin version shows 1.6.6 in the plugins list
  8. Test that network discovery, inventory, and software deployment functionality still work correctly

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

Fix this in Glpi Inventory Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26001 — 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-2026-26001 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