dbcve.org
GlpiApplication · Glpi Project

CVE-2023-35924

CRITICAL · 9.8 CVSS v3.1 Published 2023-07-05
Fix available
A fix is available. Upgrade to 10.0.8 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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. Starting in version 10.0.0 and prior to version 10.0.8, GLPI inventory endpoint can be used to drive a SQL injection attack. By default, GLPI inventory endpoint requires no authentication. Version 10.0.8 has a patch for this issue. As a workaround, one may disable native 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.7 contain an unauthenticated SQL injection vulnerability in the inventory endpoint. The endpoint accepts user input without proper sanitization and passes it directly to SQL queries, allowing attackers to execute arbitrary SQL commands. Version 10.0.8 patches the vulnerability by implementing proper input validation.

MitigationUpgrade GLPI to version 10.0.8 or later to apply the patch. Alternatively, if immediate patching is not feasible, disable the native inventory feature as a temporary workaround until the upgrade can be completed.

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.8

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. Determine your GLPI version
    Locate the version file in your GLPI installation directory (typically version.php or similar file in the root GLPI folder) and read the version number
    Affected if The installed version is 10.0.0 through 10.0.7 (any version >= 10.0.0 but < 10.0.8)
  2. Verify the inventory feature is active
    Access the GLPI administration panel and navigate to Setup > Inventory or check the configuration files for enable_inventory or similar setting
    Affected if The inventory feature is enabled in GLPI configuration
  3. Identify the inventory endpoint
    Check your web server logs or GLPI routing configuration for requests to /glpi/marketplace/inventory or similar inventory-related paths
    Affected if The inventory endpoint is accessible and accepting requests on your server
  4. Inspect inventory request handling
    Examine the PHP file handling inventory requests (typically in the inc/ or front/ directories under marketplace/inventory) for direct use of $_REQUEST or $_POST parameters in SQL queries
    Affected if User-supplied input from the inventory request is being passed directly to SQL queries without sanitization

You are affected if your GLPI version is 10.0.0 through 10.0.7 and the inventory feature is enabled, allowing unauthenticated attackers to inject malicious SQL through the inventory endpoint.

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.8 or later
Fixed in 10.0.8
Interim mitigation

Upgrade GLPI to version 10.0.8 or later to apply the patch. Alternatively, if immediate patching is not feasible, disable the native inventory feature as a temporary workaround until the upgrade can be completed.

Recommended fix High confidence

10.0.8

  1. Upgrade GLPI to version 10.0.8 to obtain the security patch for this SQL injection vulnerability
  2. After upgrading, verify that the inventory functionality continues to work as expected
  3. As an alternative mitigation (if upgrade is not immediately feasible), disable the native inventory feature in GLPI configuration
Caveat Review GLPI 10.0.8 release notes for any changes that may affect your installation

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

Fix this in Glpi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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