# CVE-2008-5071: Code injection in n/a

> Authenticated remote attackers can execute arbitrary PHP code via eval injection in the proj_id parameter of Yoxel.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **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:** 14 Nov 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-g4pw-3x2f-hxmx

## What is CVE-2008-5071?

CVE-2008-5071 is a critical code injection vulnerability in n/a, published on 14 Nov 2008. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple eval injection vulnerabilities in itpm_estimate.php in Yoxel 1.23beta and earlier allow remote authenticated users to execute arbitrary PHP code via the proj_id parameter.

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

## Which versions are affected by CVE-2008-5071?

It affects 1 product.


Products: Yoxel Yoxel.

## How do I fix CVE-2008-5071?

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

## Is CVE-2008-5071 being exploited?

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

Public exploit code:

- Yoxel 1.23beta - 'itpm_estimate.php' Remote Code Execution (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-5071 and fix it if it is affected.

What it is: CVE-2008-5071 is a critical code injection vulnerability in n/a, published on 14 Nov 2008. 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-2008-5071 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-2008-5071/ (Markdown: https://insights.sbomify.com/CVE-2008-5071/index.md)
```

## Sources

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

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