dbcve.org
GlpiApplication · Glpi Project

CVE-2023-41324

HIGH · 8.8 CVSS v3.1 Published 2023-09-27
Fix available
A fix is available. Upgrade to 10.0.10 or later.
See remediation →
94/100
Remediation priority · Urgent
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 that have read access on users resource can steal accounts of other users. 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 is a free IT asset and service management software. The vulnerability is an API authorization flaw where a user with read-only access to the users API endpoint can steal accounts of other users, likely through an IDOR (Insecure Direct Object Reference) or improper access control that allows password reset or credential theft.

MitigationUpgrade to GLPI version 10.0.10 or later. There are no known workarounds; the fix must be applied.

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.3.0, < 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Identify GLPI installation and version
    Locate the GLPI installation directory (commonly in web root like /var/www/html/glpi). Look for a version file or check the footer/login page for the version number. Common version file locations include version.php in the root or inc/.. directory.
    Affected if The installed version is >= 9.3.0 and < 10.0.10
  2. Verify API module is enabled
    Check the GLPI configuration for API settings. This is typically found in Setup > General > API, or by examining the config/database for api_enabled or similar configuration entries.
    Affected if The API functionality is enabled in GLPI configuration
  3. Confirm user API endpoint accessibility
    Attempt to access the /api/glpi/users endpoint (or /apirest.php/User) using a read-only API token or session with minimal permissions. The vulnerability exists if a user with read-only API access can enumerate or access other user records.
    Affected if A user with read-only access to the users API endpoint can view or manipulate accounts belonging to other users, indicating improper authorization control
  4. Check user account permissions
    Create or use a test account with minimal (read-only) access to the users API. Attempt to trigger password reset or credential-related operations on other user accounts through the API.
    Affected if A read-only API user can perform privileged operations on other user accounts, such as initiating password resets or accessing sensitive credential data

A user is affected if GLPI version is 9.3.0 through 10.0.9 (exclusive of 10.0.10) AND the API module is enabled, allowing a read-only API user to access or manipulate other user accounts.

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 or later. There are no known workarounds; the fix must be applied.

Recommended fix High confidence

10.0.10

  1. Create a complete backup of the GLPI database and files
  2. Download GLPI version 10.0.10 from the official source
  3. Place the application in maintenance mode if possible
  4. Extract and deploy the new version files, preserving the config directory
  5. Run the upgrade process/database migration if required
  6. Verify the installation by logging in and checking the version
  7. Test that API user permissions now properly restrict access to user resources
  8. Disable maintenance mode
Caveat Standard upgrade considerations apply - always test in non-production environment first; review release notes for any configuration or feature changes between your current version and 10.0.10

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

Fix this in Glpi Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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