# CVE-2016-5072: Code injection in OXID eShop before 2016-06-13

> Remote attackers can execute arbitrary code via requests to the oxuser class in OXID eShop, requiring an upgrade to patched versions.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/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:** 10 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6r7w-whmg-2357

## What is CVE-2016-5072?

CVE-2016-5072 is a high-severity code injection vulnerability in OXID eShop before 2016-06-13, published on 10 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OXID eShop before 2016-06-13 allows remote attackers to execute arbitrary code via a GET or POST request to the oxuser class. Fixed versions are Enterprise Edition v5.1.12, Enterprise Edition v5.2.9, Professional Edition v4.8.12, Professional Edition v4.9.9, Community Edition v4.8.12, Community Edition v4.9.9.

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

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

It affects 1 product.


Products: Oxidforge Oxid Eshop.

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

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

## Is CVE-2016-5072 being exploited?

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

## Other vulnerabilities in OXID eShop before 2016-06-13

- [CVE-2009-3112](https://insights.sbomify.com/CVE-2009-3112/): Privilege escalation in n/a (critical 10.0)
- [CVE-2023-26260](https://insights.sbomify.com/CVE-2023-26260/): Auth bypass in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-5072 is a high-severity code injection vulnerability in OXID eShop before 2016-06-13, published on 10 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-5072 in the wild and no public exploit code.

Affected product: OXID eShop before 2016-06-13. 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-5072/ (Markdown: https://insights.sbomify.com/CVE-2016-5072/index.md)
```

## Sources

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

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