Stored XSS via unencoded asset-lock output
Published Jun 3, 2026 · Updated Jun 3, 2026
Stored XSS in GLPI 10.0.4 through 10.0.24 allows remote authenticated users with technician rights to run scripts via asset locks. The asset-lock tab stores a technician-supplied payload and later renders it without the output encoding needed to prevent browser interpretation. A separate user must view the poisoned asset-lock content; the script then runs in that user's GLPI browser context and can act with that session's access.
Summary
What happened
Stored XSS in GLPI 10.0.4 through 10.0.24 allows remote authenticated users with technician rights to run scripts via asset locks. The asset-lock tab stores a technician-supplied payload and later renders it without the output encoding needed to prevent browser interpretation. A separate user must view the poisoned asset-lock content; the script then runs in that user's GLPI browser context and can act with that session's access.
The record
- CVE
- CVE-2026-42321
- Published
- Jun 3, 2026
- Updated
- Jun 3, 2026
- Vendor
- GLPI Project
- Product
- GLPI
- Classifications
- CWE-79, CWE-116, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 3, 2026CVE publishedPublication date reported by the CVE source.
- Jun 3, 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=>= 10.0.4, < 10.0.25
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
No public exploit references are available in this record.
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