dbcve.org
GlpiApplication · Glpi Project

CVE-2023-36808

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
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 0.80 and prior to version 10.0.8, Computer Virtual Machine form and GLPI inventory request can be used to perform a SQL injection attack. 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

SQL injection vulnerability in GLPI's Computer Virtual Machine form and GLPI inventory request functionality, affecting versions 0.80 through 10.0.7. This critical (CVSS 9.8) flaw allows remote attackers to inject malicious SQL queries via unsanitized input in the inventory processing logic.

MitigationUpgrade to GLPI version 10.0.8 or later which contains the patch. Alternatively, as a temporary workaround, disable native inventory functionality if upgrading is not immediately feasible.

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:>= 0.80, < 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. Identify GLPI installation and locate version file
    Locate the GLPI installation directory on your web server. Check for a version file such as version.txt, or look in the src/Glpi/Constant.php file for the version constant, or access the GLPI dashboard and check the footer for the installed version number.
    Affected if The installed version is between 0.80 and 10.0.7 inclusive.
  2. Confirm inventory module is enabled
    Log into GLPI as an administrator, navigate to Setup > Features, or check the general configuration to verify if the inventory feature is enabled. This can also be confirmed by checking if agents can connect to the inventory endpoint (typically /glpi/front/inventory.php).
    Affected if The inventory functionality is active and accessible on the GLPI instance.
  3. Verify Computer Virtual Machine form access
    Navigate to a Computer item in GLPI and check if the Virtual Machine tab or form is accessible. This is typically found under a computer's details page in the 'Virtual machines' dropdown or tab section.
    Affected if Users can access the Computer Virtual Machine management form in the GLPI interface.
  4. Check external inventory agent connectivity
    Review the GLPI inventory request functionality by examining whether the server accepts inventory data from external agents (GLPI Agent, FusionInventory) via the inventory interface. Check the server logs for incoming inventory requests.
    Affected if The GLPI instance accepts or processes inventory data from remote agents or external sources.

Your environment is affected if GLPI version 0.80 through 10.0.7 is installed AND the inventory functionality is enabled, allowing external input to reach the vulnerable Computer Virtual Machine form or inventory processing logic.

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 to GLPI version 10.0.8 or later which contains the patch. Alternatively, as a temporary workaround, disable native inventory functionality if upgrading is not immediately feasible.

Recommended fix High confidence

10.0.8

  1. 1. Back up your current GLPI database and files before upgrading.
  2. 2. Download GLPI version 10.0.8 from the official GLPI repository or website.
  3. 3. Replace the existing GLPI files with the new version 10.0.8 files.
  4. 4. Run the migration script if provided in the release to update the database schema.
  5. 5. Clear any caches (temp directories, compiled templates).
  6. 6. Verify the application is functioning correctly after upgrade.
  7. 7. Confirm the SQL injection vulnerability is resolved by testing the Computer Virtual Machine form and inventory functionality.
Caveat Review the GLPI 10.0.8 release notes for any breaking changes between your current version and 10.0.8, especially if upgrading from older minor versions

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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