CVE Tools

CVE-2023-36808

GLPI vulnerable to SQL injection through Computer Virtual Machine information

Exploitation likely. EPSS gives it a 52% chance of exploitation in the next 30 days. A vendor fix is available.

Published Updated Sources: CVE.org, NVD, BDU

What to do

The vendor has published a fix. Version details are below where the sources state them.

  • Glpi-project GlpiAffected: >= 0.80, < 10.0.8Upgrade to: not statedStated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check which version of GLPI you are running — anything from 0.80 up to just before 10.0.8 is affected.
  2. If you manage GLPI yourself, upgrade to version 10.0.8 or later as soon as possible.
  3. If a vendor or IT provider manages GLPI for you, ask them directly whether your instance has been patched.
  4. If you can't upgrade immediately, disable native inventory as a temporary measure.
  5. After upgrading, confirm the version shown in GLPI matches 10.0.8 or higher.

What it is

From the CVE record

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.

In plain language

Written by AI from the record

GLPI, a popular IT asset management tool, has a serious flaw that lets an outsider tamper with its database without even logging in — if you run GLPI, this needs attention soon, and the fix is version 10.0.8 or later.

Unauthenticated SQL injection in GLPI's Computer Virtual Machine form and inventory request handling (CWE-89) allows remote attackers to manipulate database queries without any credentials, fixed in 10.0.8.

If you're affected

  • IT asset database exposure
  • Unauthorized data extraction
  • Operational disruption
  • Compliance/audit risk

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS99th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

52% chance of exploitation activity in the next 30 days, which ranks it in the 99th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

8 events over 1188 days, from the signal feeds we watch.

  1. EPSS band changemoderate → highepss band change
  2. OpenVAS check added
  3. Patch availablerecord updated
  4. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

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

Scored 8.6 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity NoneNo integrity impact
  • Availability NoneNo availability impact

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Glpi, not every advisory.