Browser script execution via raw Content response
Published Jun 2, 2026 · Updated Jun 2, 2026
Stored XSS in GLPI before 11.0.7 allows remote authenticated users with knowledge-base write access to execute scripts in a viewer's browser. KnowbaseItemController::content() returns the stored answer field directly in the Content response instead of applying the sanitization used by the Full path. Exploitation requires knowledge-base modification rights and active viewing of the poisoned item, limiting execution to the viewer's browser session.
Summary
What happened
Stored XSS in GLPI before 11.0.7 allows remote authenticated users with knowledge-base write access to execute scripts in a viewer's browser. KnowbaseItemController::content() returns the stored answer field directly in the Content response instead of applying the sanitization used by the Full path. Exploitation requires knowledge-base modification rights and active viewing of the poisoned item, limiting execution to the viewer's browser session.
The record
- CVE
- CVE-2026-5385
- Published
- Jun 2, 2026
- Updated
- Jun 2, 2026
- Vendor
- GLPI Project
- Product
- GLPI
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 2, 2026CVE publishedPublication date reported by the CVE source.
- Jun 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <11.0.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Fluid Attacks Bizkit proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo