CVE-2026-40108
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. In versions 11.0.0 through 11.0.6, a technician can store an XSS payload in a ITIL costs. This issue has been fixed in version 11.0.7.
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 confidenceStored XSS vulnerability in GLPI versions 11.0.0 through 11.0.6 allows authenticated technicians to inject malicious JavaScript payloads into ITIL cost fields. When other users view the affected cost data, the embedded script executes in their browser session, potentially enabling session hijacking or further attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Privileges
- High
- Authentication
- X
- User interaction
- A
- Scope
- X
CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 installation and versionLocate the GLPI installation directory and check the version file (typically version.php or similar file containing the version string). Alternatively, access GLPI's about page or check the database version record.Affected if The installed version is 11.0.0, 11.0.1, 11.0.2, 11.0.3, 11.0.4, 11.0.5, or 11.0.6
-
Confirm ITIL cost fields are in useCheck if tickets, problems, or changes in GLPI have cost-related fields configured. Examine whether users have created items with cost data entered in ITIL objects.Affected if ITIL cost fields (ticket/problem/change costs) have been used and cost data exists in the system
-
Examine cost field data for malicious scriptsQuery the database or inspect ITIL object records containing cost information. Look for HTML or JavaScript code within cost value fields.Affected if Cost fields contain unexpected HTML tags, script elements, or JavaScript event handlers that were not entered by administrators
-
Review audit logs for suspicious cost field modificationsCheck GLPI's internal logs or history tables for recent changes to cost fields, particularly from technician accounts, containing unusual character patterns.Affected if Recent cost field modifications contain encoded or obfuscated JavaScript payloads
A user is affected if they run GLPI version 11.0.0 through 11.0.6 and have cost data entered in ITIL objects, as the stored XSS could execute when other users view that data.
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 · scopedUpgrade GLPI to version 11.0.7 or later to remediate this vulnerability.
GLPI 11.0.7
- 1. Backup your current GLPI database and files before performing the upgrade.
- 2. Download GLPI version 11.0.7 from the official source (github.com/glpi-project/glpi or get.glpi-project.org).
- 3. Replace the existing GLPI installation files with the new version 11.0.7 files, or use the appropriate upgrade method for your deployment.
- 4. Verify the upgrade was successful by logging into GLPI.
- 5. Confirm the XSS vulnerability in ITIL costs is resolved by testing that HTML/script tags are properly sanitized when entered in cost fields.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40108 — 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-2026-40108 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