CVE-2025-59935VulnerabilityPublished 16 Dec 2025

CVE-2025-59935: glpi · Cross-site Scripting

Affects glpiSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 10.0.21 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 10.0.21

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade glpi-project/glpi to 10.0.21.

Affected software

Product	Affected	Fixed in
GitHubglpi-project/glpi`pkg:github/glpi-project/glpi`Other threats	Affected 10.0.0 <10.0.21	Fixed in 10.0.21

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The primary mitigation is to upgrade GLPI installations to version 10.0.21 or later, where the vulnerability has been patched. Organizations should implement strict input validation and output encoding on all user-supplied data, especially on the inventory endpoint, to prevent injection of malicious scripts. Web application firewalls (WAFs) can be configured to detect and block common XSS payload patterns targeting GLPI endpoints. Security teams should monitor logs for unusual or repeated requests to the inventory endpoint that may indicate exploitation attempts. User awareness training should emphasize caution when interacting with inventory pages and recognizing potential phishing attempts that could trigger XSS payloads. Additionally, applying Content Security Policy (CSP) headers can help mitigate the impact of XSS by restricting script execution sources. Regular vulnerability scanning and penetration testing focused on web application security will help identify any residual or related weaknesses. Finally, organizations should review and limit GLPI user permissions to reduce the impact scope if exploitation occurs.

Description

CVE-2025-59935 is a medium severity cross-site scripting (XSS) vulnerability affecting glpi-project's GLPI software versions 10.0.0 up to but not including 10.0.21. An unauthenticated attacker can inject malicious scripts via the inventory endpoint, which requires user interaction to trigger. The vulnerability impacts confidentiality by potentially stealing sensitive user data through script execution but does not affect integrity or availability. No known exploits are currently reported in the wild. European organizations using vulnerable GLPI versions for IT asset management should prioritize upgrading to version 10.0.

Impact

For European organizations, this vulnerability poses a risk primarily to confidentiality, as attackers can steal sensitive data from users interacting with the GLPI inventory interface. Since GLPI is used for IT asset management, exposure of inventory data or session credentials could facilitate further lateral movement or targeted attacks within an organization. The unauthenticated nature of the injection increases the attack surface, allowing external threat actors to attempt exploitation without credentials. Although no integrity or availability impact is noted, the potential for data leakage and subsequent exploitation could disrupt operations or lead to compliance violations under GDPR if personal or sensitive data is exposed. Organizations relying heavily on GLPI for managing critical infrastructure or governmental IT assets are at heightened risk. The requirement for user interaction means social engineering or phishing campaigns could be used to trigger the payload, increasing the threat to end users. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate it, especially as the vulnerability is publicly disclosed.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/glpi-project/glpi/security/advisories/GHSA-j8vv-9f8m-r7jx (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Dec 2025, 17:22 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats