dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-42321

HIGH · 8.4 CVSS v4.0 Published 2026-06-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
Remotely reachable

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 · unedited
GLPI is a free asset and IT management software package. Starting in version 10.0.4 and prior to version 10.0.25, a technician can store an XSS payload in the asset locked tab. Upgrade to 10.0.25 or 11.0.7 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 confidence

GLPI versions 10.0.4 through 10.0.24 and 11.x before 11.0.7 contain a stored cross-site scripting (XSS) vulnerability in the asset locked tab. An authenticated technician can inject malicious JavaScript code that executes when other users view the affected asset, due to insufficient input sanitization of the locked tab content.

MitigationUpgrade GLPI to version 10.0.25 or 11.0.7 or later to patch the XSS vulnerability. Restrict technician-level access until the upgrade is applied if the risk is deemed unacceptable.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm GLPI installation
    Check for GLPI installation by looking for the 'glpi' directory in web root (commonly /var/www/html/glpi, /www/glpi, or C:\inetpub\wwwroot\glpi) and locating the version.php file within the codebase.
    Affected if GLPI is not installed or cannot be located.
  2. Determine installed GLPI version
    Open the version.php file in the GLPI root directory and read the 'version' or 'glpi_version' variable to identify the exact version number.
    Affected if Version is between 10.0.4 and 10.0.24 inclusive, or 11.x prior to 11.0.7.
  3. Verify technician role access
    Log into GLPI as an administrator and navigate to Administration > Users to confirm if technician-level accounts exist with access to asset management functionality.
    Affected if Technician accounts with asset access are present in the system.
  4. Confirm asset locked tab functionality
    As a technician user, navigate to an asset item (such as a computer or peripheral) and verify if the 'Locked' or 'Verouillé' tab is visible and accessible in the asset details page.
    Affected if The asset locked tab feature is present and accessible to authenticated users.

The environment is affected if GLPI version 10.0.4 through 10.0.24 or 11.x prior to 11.0.7 is installed AND the asset locked tab is accessible to authenticated technician users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade GLPI to version 10.0.25 or 11.0.7 or later to patch the XSS vulnerability. Restrict technician-level access until the upgrade is applied if the risk is deemed unacceptable.

Recommended fix High confidence

10.0.25 or 11.0.7

  1. Backup the GLPI database and all files before proceeding with the upgrade
  2. Download GLPI version 10.0.25 or 11.0.7 from the official GitHub repository (github.com/glpi-project/glpi) or the official website
  3. Extract the new version files to the web server document root
  4. Copy the config directory from the old installation to preserve database connection settings
  5. Ensure file permissions are correctly set (typically www-data or apache user ownership)
  6. Run the upgrade by accessing the GLPI web interface - it will automatically detect and upgrade the database
  7. Clear any cached data (delete files in the tmp/ and cache/ directories)
  8. Verify the installation by logging in and checking the asset locked tab functionality
Caveat Major version upgrades (e.g., 10.x to 11.x) may have breaking changes; review release notes before upgrading and test in a staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42321 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-42321 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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