# CVE-2016-6175: Code injection in n/a

> Remote attackers can execute arbitrary PHP code via a crafted plural forms header in the php-gettext library.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Feb 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-6175, GHSA-6f39-vhv8-5hcw, UBUNTU-CVE-2016-6175

## What is CVE-2016-6175?

CVE-2016-6175 is a critical code injection vulnerability in n/a, published on 7 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Eval injection vulnerability in php-gettext 1.0.12 and earlier allows remote attackers to execute arbitrary PHP code via a crafted plural forms header.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Php-Gettext Project Php-Gettext.

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

Upgrade to a fixed version.

## Is CVE-2016-6175 being exploited?

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

Public exploit code:

- PHP gettext 1.0.12 - 'gettext.php' Code Execution (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6175 and fix it if it is affected.

What it is: CVE-2016-6175 is a critical code injection vulnerability in n/a, published on 7 Feb 2017. 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-2016-6175 exists.

Affected product: n/a. 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-6175/ (Markdown: https://insights.sbomify.com/CVE-2016-6175/index.md)
```

## Sources

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

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