dbcve.org
GlpiApplication · Glpi Project

CVE-2026-26027

MEDIUM · 6.1 CVSS v3.1 Published 2026-04-06
Fix available
A fix is available. Upgrade to 11.0.6 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 to before 11.0.6, an unauthenticated user can store an XSS payload through the inventory endpoint. This vulnerability is fixed in 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 · moderate confidence

GLPI versions 11.0.0 through 11.0.5 contain a stored XSS vulnerability in the inventory endpoint that allows unauthenticated attackers to inject malicious JavaScript payloads. The injected script persists in the system and executes when other users access the compromised inventory data.

MitigationUpgrade GLPI to version 11.0.6 or later to apply the security patch. Until then, consider restricting access to the inventory endpoint or implementing WAF rules to block suspicious input.

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.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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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. Determine installed GLPI version
    Locate the version file in your GLPI installation directory, typically at 'version.php' or check the footer of the GLPI web interface for the version number
    Affected if The installed version is 11.0.0, 11.0.1, 11.0.2, 11.0.3, 11.0.4, or 11.0.5
  2. Verify inventory feature is enabled
    Access the GLPI administration panel and navigate to Setup > General > Inventory to confirm the inventory feature is turned on
    Affected if The inventory feature is enabled and accessible to unauthenticated users
  3. Check inventory endpoint accessibility
    Attempt to access the inventory endpoint URL (typically /front/inventory.php or /ajax/inventory.php) without authentication to determine if it accepts external input
    Affected if The endpoint is reachable without authentication and accepts POST or GET parameters containing inventory data
  4. Review recent inventory imports for suspicious content
    Examine the inventory import history in GLPI (Administration > Inventory > Import History) for any unexpected or encoded JavaScript tags, script elements, or event handler attributes in imported data
    Affected if Any inventory records contain unescaped HTML tags, script elements, or JavaScript event handlers in data fields

You are affected if your GLPI version is 11.0.0 through 11.0.5 and the inventory endpoint is accessible to unauthenticated users or has accepted external inventory data.

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.6 or later
Fixed in 11.0.6
Interim mitigation

Upgrade GLPI to version 11.0.6 or later to apply the security patch. Until then, consider restricting access to the inventory endpoint or implementing WAF rules to block suspicious input.

Recommended fix High confidence

11.0.6

  1. 1. Back up your current GLPI installation and database before proceeding with any upgrade.
  2. 2. Download GLPI version 11.0.6 from the official source (github.com/glpi-project/glpi or get.glpi-project.org).
  3. 3. Follow the standard GLPI upgrade procedure: replace the existing files with the new version 11.0.6 files, keeping the config directory intact.
  4. 4. Run the migration scripts if prompted during the upgrade process.
  5. 5. Verify the upgrade was successful by accessing the GLPI interface.
  6. 6. Test the inventory endpoint to confirm the XSS vulnerability is no longer present.

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

Fix this in Glpi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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