# CVE-2016-7508: SQL injection in n/a

> Authenticated attackers can execute arbitrary SQL commands in GLPI when the database uses Big5 encoding, allowing data access or modification.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jun 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8vx9-fq6p-x4r8, UBUNTU-CVE-2016-7508

## What is CVE-2016-7508?

CVE-2016-7508 is a high-severity SQL injection vulnerability in Glpi-Project Glpi, published on 21 Jun 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in GLPI 0.90.4 allow an authenticated remote attacker to execute arbitrary SQL commands by using a certain character when the database is configured to use Big5 Asian encoding.

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

## Which versions are affected by CVE-2016-7508?

It affects 1 product.


Products: Glpi-Project Glpi.

## How do I fix CVE-2016-7508?

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

## Is CVE-2016-7508 being exploited?

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

Public exploit code:

- GLPI 0.90.4 - SQL Injection (exploitdb)

## 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-2016-7508 and fix it if it is affected.

What it is: CVE-2016-7508 is a high-severity SQL injection vulnerability in Glpi-Project Glpi, published on 21 Jun 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-7508 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-2016-7508/ (Markdown: https://insights.sbomify.com/CVE-2016-7508/index.md)
```

## Sources

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

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