# CVE-2026-11321: GLPI DataInjection Plugin Authenticated SQL Injection via CSV Import

> Authenticated users can exploit SQL injection in the GLPI DataInjection plugin's CSV import feature to extract database information via time-based blind attacks.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-57qv-j6r6-pcc4, GHSA-q93h-qc46-87rr

## What is CVE-2026-11321?

CVE-2026-11321 is a high-severity SQL injection vulnerability in pluginsGLPI datainjection, published on 10 Jul 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The DataInjection plugin for GLPI 2.15.6 (GLPI 11 builds) concatenates user-supplied CSV field values directly into SQL queries during CSV import, without parameterization or escaping, resulting in authenticated SQL injection. An authenticated user with access to the Data injection feature can embed SQL expressions such as SLEEP() in a mapped field (for example Serial Number) to manipulate the generated query and extract database information via time-based blind injection.

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

## Which versions are affected by CVE-2026-11321?


## How do I fix CVE-2026-11321?

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

## Is CVE-2026-11321 being exploited?

There is no known exploitation of CVE-2026-11321 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-11321 and fix it if it is affected.

What it is: CVE-2026-11321 is a high-severity SQL injection vulnerability in pluginsGLPI datainjection, published on 10 Jul 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-11321 in the wild and no public exploit code.

Affected product: pluginsGLPI datainjection. 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-2026-11321/ (Markdown: https://insights.sbomify.com/CVE-2026-11321/index.md)
```

## Sources

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

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