# CVE-2025-24799: GLPI allows unauthenticated SQL injection through the inventory endpoint

> Unauthenticated attackers can execute SQL injection via the inventory endpoint in GLPI, potentially reading or modifying database contents.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Mar 2025
- **Updated:** 18 Mar 2025
- **Also known as:** GHSA-jv89-g7f7-jwfg, UBUNTU-CVE-2025-24799

## What is CVE-2025-24799?

CVE-2025-24799 is a high-severity SQL injection vulnerability in Glpi-Project Glpi, published on 18 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GLPI is a free asset and IT management software package. An unauthenticated user can perform a SQL injection through the inventory endpoint. This vulnerability is fixed in 10.0.18.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2025-24799?

It affects 1 product.


Products: Glpi-Project Glpi.

## How do I fix CVE-2025-24799?

No fix has been published for CVE-2025-24799 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-24799 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-24799 exists.

Public exploit code:

- CVE-2025-24799 Exploit: GLPI - Unauthenticated SQL Injection (github_poc): https://github.com/MatheuZSecurity/Exploit-CVE-2025-24799
- CVE-2025-24799 SQLi Scanner (github_poc): https://github.com/MuhammadWaseem29/CVE-2025-24799
- GLPI Inventory Plugin Unauthenticated Blind Boolean SQLi (metasploit)
- CVE-2025-24799 Exploit: GLPI - Unauthenticated SQL Injection (github_poc): https://github.com/Rosemary1337/CVE-2025-24799
- Scanner for GLPI CVE-2025-24799 vulnerability (github_poc): https://github.com/airbus-cert/CVE-2025-24799-scanner
- https://github.com/galisko/CVE-2025-24799 (github_poc): https://github.com/galisko/CVE-2025-24799

## Other vulnerabilities in Glpi-Project Glpi

- [CVE-2022-35914](https://insights.sbomify.com/CVE-2022-35914/): Teclib GLPI Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2023-42802](https://insights.sbomify.com/CVE-2023-42802/): GLPI vulnerable to unallowed PHP script execution (critical 10.0)
- [CVE-2023-28849](https://insights.sbomify.com/CVE-2023-28849/): GLPI vulnerable to SQL injection and Stored XSS via inventory agent request (critical 10.0)
- [CVE-2022-35947](https://insights.sbomify.com/CVE-2022-35947/): SQL injection in GLPI (critical 10.0)
- [CVE-2022-31056](https://insights.sbomify.com/CVE-2022-31056/): SQL injection with _actor parameter in GLPI (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24799 and fix it if it is affected.

What it is: CVE-2025-24799 is a high-severity SQL injection vulnerability in Glpi-Project Glpi, published on 18 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-24799 exists.

Affected product: Glpi-Project Glpi. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-24799/ (Markdown: https://insights.sbomify.com/CVE-2025-24799/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-24799
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-24799
- OSV: https://osv.dev/vulnerability/CVE-2025-24799

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-24799/
Summaries are generated and may contain mistakes; the official description above is the record.