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

> Remote attackers can inject arbitrary PHP code into OxYBox via the oxymsg parameter, leading to code execution.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Apr 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cxv6-gvcr-65jm

## What is CVE-2008-6651?

CVE-2008-6651 is a critical code injection vulnerability in n/a, published on 7 Apr 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Static code injection vulnerability in edithistory.php in OxYProject OxYBox 0.85 allows remote attackers to inject arbitrary PHP code into oxyhistory.php via the oxymsg parameter.

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

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

It affects 1 product.


Products: Oxyproject Oxybox.

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

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

## Is CVE-2008-6651 being exploited?

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

Public exploit code:

- OxYProject 0.85 - 'edithistory.php' Remote Code Execution (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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