CVE-2026-5385
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 · uneditedAn unauthenticated user with write access to the knowledge base can store an XSS payload in a knowledge base item. This issue affects glpi: before 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 confidenceA stored Cross-Site Scripting (XSS) vulnerability in GLPI's knowledge base feature allows an unauthenticated user with write access to inject malicious JavaScript code into knowledge base items. When other users view these items, the embedded script executes in their browsers, potentially stealing session cookies or performing actions on behalf of the victim.
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
- Low
- Privileges
- High
- Authentication
- X
- User interaction
- A
- Scope
- X
CVSS:4.0/AV:N/AC:L/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 the installed GLPI versionLocate the version file or admin panel (typically at /glpi/version.txt or in the Administration > Setup > General section). Compare your version number to the affected range (versions prior to 11.0.7).Affected if Your GLPI version is 11.0.6 or earlier, or any version prior to 11.0.7.
-
Verify knowledge base access settingsNavigate to Administration > Setup > General > Knowledge Base in the GLPI admin panel. Check whether the option allowing unauthenticated (public) users to write to the knowledge base is enabled.Affected if The knowledge base is configured to permit write access from unauthenticated/public users.
-
Examine knowledge base entries for suspicious contentAccess the knowledge base as an administrator and review recent items (Knowledge Base > Management). Look for entries containing script tags, javascript: URIs, event handlers (onload, onerror, onclick), or Base64-encoded strings that may obfuscate malicious code.Affected if Any knowledge base item contains JavaScript code, script tags, or suspicious event handlers that were not created by an administrator.
-
Check browser console for XSS errors when viewing knowledge baseLog in as a regular user (not admin), navigate to the public knowledge base, and open the browser developer console (F12). Look for any script execution errors or injected scripts loading unexpectedly.Affected if When viewing knowledge base items as a non-admin user, JavaScript code executes or console errors indicate reflected malicious content.
You are affected if your GLPI version is prior to 11.0.7 AND the knowledge base allows write access for unauthenticated users, or if malicious script content already exists in your knowledge base.
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 which includes proper input sanitization and output encoding for knowledge base content to prevent XSS execution.
GLPI 11.0.7
- Backup your current GLPI database and files before proceeding with any upgrade
- Download GLPI version 11.0.7 from the official GitHub releases page (github.com/glpi-project/glpi) or the official GLPI website
- Replace the existing GLPI files with the new version 11.0.7 files, preserving your configuration and custom files
- Run the GLPI upgrade script by accessing the web interface and following the upgrade prompts
- Verify the installation by logging in and checking that the knowledge base functionality works correctly
- Test that the XSS vulnerability is patched by verifying that script tags cannot be stored in knowledge base items
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5385 — 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-5385 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