dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-42320

MEDIUM · 5.9 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 →
65/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 0.50 and prior to versions 10.0.25 and 11.0.7, a technician can read arbitrary files inside the GLPI_DOC_DIR. 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

An authenticated technician user can read arbitrary files within the GLPI_DOC_DIR directory due to insufficient access controls, allowing potential exposure of sensitive configuration or system files on the server.

MitigationUpgrade GLPI to version 10.0.25 or 11.0.7 to apply the patch that fixes the arbitrary file read vulnerability.

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
High
Privileges
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/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 and locate configuration
    Search for GLPI installation directories (commonly /var/www/html/glpi, /opt/glpi, or C:\inetpub\wwwroot\glpi) and locate the config/config_db.php or config/glpi.yml file that contains database credentials and version information
    Affected if GLPI is installed and accessible on the system
  2. Identify installed GLPI version
    Open the version file (typically at inc/GLPI_VERSION, config/VERSION, or in the database glpi_configs table) and note the exact version number
    Affected if The installed version is earlier than 10.0.25 or 11.0.7, or the version cannot be determined (unknown/older release)
  3. Verify GLPI_DOC_DIR configuration
    Check the GLPI configuration file (config/config.php or config/glpi.yml) or database for the GLPI_DOC_DIR directive which defines the document storage path
    Affected if GLPI_DOC_DIR is configured and points to a readable directory on the system
  4. Confirm technician-level user access
    Log into GLPI as a technician-level user and verify the account has access to the ticket/document management features where the path traversal could be exploited
    Affected if An authenticated user with technician privileges or higher can access the GLPI interface

A user is affected if running any GLPI version below 10.0.25 or 11.0.7 where GLPI_DOC_DIR is configured and the attacker has technician-level authentication to exploit the path traversal.

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 to apply the patch that fixes the arbitrary file read vulnerability.

Recommended fix High confidence

10.0.25 or 11.0.7

  1. 1. Back up the current GLPI installation and database before proceeding with the upgrade.
  2. 2. Download GLPI version 10.0.25 or 11.0.7 from the official source (github.com/glpi-project/glpi).
  3. 3. Extract the new version files to your web server document root, replacing the existing installation.
  4. 4. Run the GLPI upgrade process by accessing the application via web browser or command line.
  5. 5. Verify the upgrade was successful by logging in and testing core functionality.
  6. 6. Confirm the arbitrary file read vulnerability is no longer present.
Caveat Review release notes for any security or configuration changes between your current version and the target version

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
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42320 — 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-42320 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