Security Resilience

CVE-2023-43813

SQLi in Glpi-Project Glpi 10.0.0 – 10.0.11

Published
13 December 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.31 98th percentile
Risk Priority 66 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-43813 is a medium-severity SQL Injection (CWE-89) vulnerability in Glpi-Project Glpi. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Protocol or Service Impersonation (T1001.003); ranked in the top 2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

GLPI, an open-source IT asset management application, contains a SQL injection vulnerability in its saved search feature. The flaw affects all releases from 10.0.0 through 10.0.10 and is tracked as CWE-89. It received a CVSS 3.1 score of 6.5, reflecting network attack vector, low complexity, and low privileges required.

An authenticated user can supply a crafted saved-search payload that is processed without adequate parameterization, allowing the attacker to read arbitrary database contents. Because the injection occurs server-side with no user-interaction requirement, an adversary with a valid account can exfiltrate sensitive configuration or asset data across the network.

The project addressed the issue in version 10.0.11; the corrective commit and corresponding GitHub Security Advisory GHSA-94c3-fw5r-3362 are publicly available. Administrators should upgrade to 10.0.11 or later and verify that the saved-search code path no longer accepts unsanitized input.

EPSS for the CVE currently stands at 0.1147 with a recorded peak of 0.1174; no material post-disclosure climb from a low baseline is evident, and no confirmed in-the-wild exploitation has been reported.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

GLPI is a free asset and IT management software package. Starting in version 10.0.0 and prior to version 10.0.11, the saved search feature can be used to perform a SQL injection. Version 10.0.11 contains a patch for the issue.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.003 Protocol or Service Impersonation Command And Control
Adversaries may impersonate legitimate protocols or web service traffic to disguise command and control activity and thwart analysis efforts.
T1003 OS Credential Dumping Credential Access
Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password.
T1003.001 LSASS Memory Credential Access
Adversaries may attempt to access credential material stored in the process memory of the Local Security Authority Subsystem Service (LSASS).
T1003.002 Security Account Manager Credential Access
Adversaries may attempt to extract credential material from the Security Account Manager (SAM) database either through in-memory techniques or through the Windows Registry where the SAM database is stored.
T1003.003 NTDS Credential Access
Adversaries may attempt to access or create a copy of the Active Directory domain database in order to steal credential information, as well as obtain other information about domain members such as devices, users, and access rights.
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-37278Same product: Glpi-Project Glpi
CVE-2024-31456Same product: Glpi-Project Glpi
CVE-2023-42461Same product: Glpi-Project Glpi
CVE-2023-46727Same product: Glpi-Project Glpi
CVE-2023-36808Same product: Glpi-Project Glpi
CVE-2023-28838Same product: Glpi-Project Glpi
CVE-2024-29889Same product: Glpi-Project Glpi
CVE-2023-35924Same product: Glpi-Project Glpi
CVE-2024-27096Same product: Glpi-Project Glpi
CVE-2024-37148Same product: Glpi-Project Glpi

Affected Assets

glpi-project
glpi
10.0.0 — 10.0.11

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V6.2.5

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-89

Penetration testing uses SQL injection payloads against database interfaces, identifying and supporting fixes for SQL injection weaknesses.

addresses: CWE-89

Validates query inputs to prevent SQL syntax or command manipulation.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly target injection flaws during coding and review so largely prevent CWE-89 introduction, yet the single broad outcome leaves residual risk from incomplete neutralization techniques or missed edge cases.

PR.AT-02 partial match
blocks

Training raises developer awareness of SQLi risks and can reduce introduction likelihood (partial) but removes none of the actual coding flaw's risk by itself since technical neutralization is still required.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

removes
removes
removes
removes
blocks

A.5.6 only improves knowledge flow, awareness of threats/patches and access to specialist advice; it does not stop SQL injection from being exploitable in code that still contains the flaw.

References