dbcve.org
GlpiApplication · Glpi Project

CVE-2023-41321

MEDIUM · 6.5 CVSS v3.1 Published 2023-09-27
Fix available
A fix is available. Upgrade to 10.0.10 or later.
See remediation →
71/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 stands for Gestionnaire Libre de Parc Informatique is a Free Asset and IT Management Software package, that provides ITIL Service Desk features, licenses tracking and software auditing. An API user can enumerate sensitive fields values on resources on which he has read access. Users are advised to upgrade to version 10.0.10. There are no known workarounds for this vulnerability.

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 · moderate confidence

GLPI versions before 10.0.10 contain an information disclosure vulnerability in the API where users with read access to certain resources can enumerate sensitive field values that should not be exposed through the API interface.

MitigationUpgrade to GLPI version 10.0.10. No workarounds are available.

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:>= 9.1.1, < 10.0.10

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Locate the GLPI installation
    Find the GLPI web application directory on your server. The version information is typically stored in a version.php or inc/VERSION.php file in the GLPI root directory.
    Affected if GLPI is installed and the version file exists in the expected location
  2. Determine the installed GLPI version
    Open the version file (version.php or inc/VERSION.php) and read the version number. Compare this to the affected range of >= 9.1.1 and < 10.0.10.
    Affected if The installed version is 9.1.1 or higher but lower than 10.0.10
  3. Verify the API is accessible
    Check if the GLPI REST API endpoint is enabled and reachable. This is typically accessible at /apirest.php or /api/ on the GLPI web server. Review the API configuration in Setup > General > API or check the apirest.php file.
    Affected if The API endpoint is accessible and the GLPI version falls within the affected range
  4. Confirm user read access to API resources
    Identify users or API tokens that have read-only access to GLPI resources (such as tickets, users, or other objects). Test whether these users can retrieve sensitive field values through API calls that should not be exposed.
    Affected if Users with read-only permissions can enumerate sensitive field values through the API that should be restricted

Your environment is affected if GLPI version is 9.1.1 or higher but lower than 10.0.10, the API is accessible, and users with read access can obtain sensitive field values through API endpoints.

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.10 or later
Fixed in 10.0.10
Interim mitigation

Upgrade to GLPI version 10.0.10. No workarounds are available.

Recommended fix High confidence

10.0.10

  1. 1. Create a complete backup of the GLPI database and filesystem (including the glpi/ directory and configuration files)
  2. 2. Review the GLPI 10.0.10 release notes for any configuration or behavioral changes
  3. 3. Test the upgrade in a staging environment before applying to production
  4. 4. Download GLPI version 10.0.10 from the official source (glpi-project.org)
  5. 5. Put the application in maintenance mode or ensure no active sessions during upgrade
  6. 6. Replace the existing GLPI files with the new version 10.0.10 files, preserving local configuration
  7. 7. Run the GLPI migration scripts by accessing the application URL or via CLI
  8. 8. Verify the upgrade was successful by logging in and checking the version number
Caveat Review release notes for configuration changes between your current version and 10.0.10; standard upgrade risks apply (test in staging first)

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

Fix this in Glpi Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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