dbcve.org
GlpiApplication · Glpi Project

CVE-2023-41320

CRITICAL · 9.8 CVSS v3.1 Published 2023-09-27
Fix available
A fix is available. Upgrade to 10.0.10 or later.
See remediation →
100/100
Remediation priority · Urgent
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 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. UI layout preferences management can be hijacked to lead to SQL injection. This injection can be use to takeover an administrator account. 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 · high confidence

GLPI (Free Asset and IT Management Software) versions prior to 10.0.10 contain a SQL injection vulnerability in the UI layout preferences management feature. This critical flaw allows unauthenticated attackers to inject malicious SQL queries, which can be leveraged to escalate privileges and takeover administrator accounts.

MitigationUpgrade GLPI to version 10.0.10 or later. There are no known workarounds; patching is the only remediation path.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate GLPI installation
    Check for GLPI in common web directories (e.g., /var/www/html/glpi, /htdocs/glpi) or search for files like glpi/inc/commonitilobject.class.php or glpi/install/install.php
    Affected if GLPI software is found on the system
  2. Determine installed GLPI version
    Open the file 'glpi/VERSION' or 'glpi/src/DbUtils.php' and look for the version string, or log into the GLPI admin panel and check the homepage footer for the version number
    Affected if The version is 10.0.0, 10.0.1, 10.0.2, 10.0.3, 10.0.4, 10.0.5, 10.0.6, 10.0.7, 10.0.8, or 10.0.9 (any version >=10.0.0 but <10.0.10)
  3. Verify UI layout preferences feature is accessible
    Check that the web server is running and the GLPI application is accessible. The vulnerable endpoint is in the user preferences/UI layout settings area, typically accessible at /glpi/front/preference.php or /glpi/ajax/uLayoutUpdate.php
    Affected if The GLPI web interface is reachable and the preferences module is enabled
  4. Confirm unauthenticated access exposure
    Verify whether the GLPI instance is exposed to the network without authentication requirements, or test accessing the preferences endpoint without logging in
    Affected if The application is accessible to unauthenticated network attackers (not behind VPN, not disabled, not requiring auth)

You are affected if GLPI version is 10.0.0 through 10.0.9 inclusive, the web interface is accessible, and the UI layout preferences feature is enabled and exposed 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.10 or later
Fixed in 10.0.10
Interim mitigation

Upgrade GLPI to version 10.0.10 or later. There are no known workarounds; patching is the only remediation path.

Recommended fix High confidence

10.0.10

  1. 1. Backup your GLPI database and files before upgrading.
  2. 2. Download GLPI version 10.0.10 from the official source (github.com/glpi-project/glpi/releases or getglpi.org).
  3. 3. Follow the official upgrade instructions: replace the existing GLPI files with the new version while preserving the config/ and files/ directories.
  4. 4. Verify the upgrade was successful by logging into the application.
  5. 5. Confirm the version displayed in the administrator interface shows 10.0.10.

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

Fix this in Glpi Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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