dbcve.org
GlpiApplication · Glpi Project

CVE-2023-22500

HIGH · 7.5 CVSS v3.1 Published 2023-01-26
Fix available
A fix is available. Upgrade to 10.0.6 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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. Versions 10.0.0 and above, prior to 10.0.6 are vulnerable to Incorrect Authorization. This vulnerability allow unauthorized access to inventory files. Thus, if anonymous access to FAQ is allowed, inventory files are accessbile by unauthenticated users. This issue is patched in version 10.0.6. As a workaround, disable native inventory and delete inventory files from server (default location is `files/_inventory`).

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.0 through 10.0.5 have an incorrect authorization vulnerability that allows unauthenticated users to access inventory files if anonymous FAQ access is enabled. The flaw permits unauthorized access to the files/_inventory directory without proper authentication.

MitigationUpgrade GLPI to version 10.0.6 or later. As a workaround, disable native inventory functionality and delete existing inventory files from the files/_inventory directory on the server.

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
GlpiApplication
Affected:>= 10.0.0, < 10.0.6

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

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

  1. Check installed GLPI version
    Locate the version file (typically VERSION or inc/html.php at the root of the GLPI installation) or access the GLPI login page footer which often displays the version number
    Affected if Version is 10.0.0 through 10.0.5 (anything >= 10.0.0 but < 10.0.6)
  2. Verify if anonymous FAQ access is enabled
    Navigate to GLPI Administration > Setup > General > Authentication tab (or equivalent) and check if the option allowing anonymous FAQ access is turned on. This setting may also be found in Configuration > Authentication > Other authentication settings
    Affected if Anonymous FAQ access is enabled in the GLPI configuration
  3. Confirm the files/_inventory directory exists
    On the GLPI server filesystem, check for the existence of the files/_inventory directory at the GLPI root installation path (e.g., /var/www/html/glpi/files/_inventory or similar)
    Affected if The files/_inventory directory exists on the server
  4. Verify inventory files are present
    List the contents of the files/_inventory directory to see if any inventory files (XML, JSON, or other inventory data files) are stored there
    Affected if Inventory files exist in the files/_inventory directory

You are affected if running GLPI version 10.0.0 through 10.0.5 AND anonymous FAQ access is enabled AND inventory files exist in the files/_inventory directory accessible to unauthenticated 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
Upgrade available Upgrade to 10.0.6 or later
Fixed in 10.0.6
Interim mitigation

Upgrade GLPI to version 10.0.6 or later. As a workaround, disable native inventory functionality and delete existing inventory files from the files/_inventory directory on the server.

Recommended fix High confidence

10.0.6

  1. Upgrade GLPI to version 10.0.6 or later to patch the vulnerability
  2. As an alternative workaround (if upgrade is not immediately possible): Disable native inventory in GLPI configuration
  3. Delete existing inventory files from the server at the default location: files/_inventory

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

Fix this in Glpi Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,950
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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