CVE-2025-59935
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. Starting in version 10.0.0 and prior to version 10.0.21, an unauthenticated user can store an XSS payload through the inventory endpoint. Users should upgrade to 10.0.21 to receive a patch.
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 confidenceGLPI versions 10.0.0 through 10.0.20 contain a stored Cross-Site Scripting (XSS) vulnerability in the inventory endpoint. An unauthenticated attacker can inject malicious JavaScript payloads that persist and execute when other users access the affected functionality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 10.0.0, < 10.0.21CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 versionLocate the version.php file in the GLPI root directory (e.g., src/Version.php or version.php) and read the version number defined in it, or access the GLPI web interface and check the 'Setup > General > System Information' page which displays the installed version.Affected if The displayed version falls within 10.0.0 through 10.0.20 (inclusive)
-
Confirm inventory feature is enabledCheck the GLPI configuration file (config/config_db.php or the database glpi_config table) for the 'inventory' feature setting, or navigate to Setup > Features in the web interface and verify if the inventory functionality is turned on.Affected if The inventory feature is enabled in the GLPI configuration
-
Inspect inventory endpoint for injected contentAccess the GLPI database and query the table that stores inventory data (typically glpi_agents or similar inventory-related tables) for any unexpected or obfuscated JavaScript tags, event handlers (onerror, onload, onclick), or suspicious URL patterns that could indicate XSS payloads.Affected if Records in inventory-related tables contain unsanitized script tags, javascript: URIs, or HTML event handler attributes
You are affected if your GLPI version is between 10.0.0 and 10.0.20 AND the inventory feature is enabled AND malicious scripts are found stored in inventory data tables.
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 · scoped10.0.21
Upgrade GLPI to version 10.0.21 which contains the vendor patch for this vulnerability. Verify the inventory endpoint properly sanitizes user input after the upgrade.
10.0.21
- Upgrade GLPI to version 10.0.21 or later by following the official upgrade documentation at https://glpi-install.readthedocs.io/en/latest/upgrade.html
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-2025-59935 — 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-2025-59935 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