# CVE-2006-5291: Code injection in n/a

> Remote attackers can execute arbitrary PHP code via a URL parameter in the SPAW Editor component of Download-Engine.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cg2v-qgrr-gw86

## What is CVE-2006-5291?

CVE-2006-5291 is a high-severity code injection vulnerability in n/a, published on 16 Oct 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PHP remote file inclusion vulnerability in admin/includes/spaw/spaw_control.class.php in Download-Engine 1.4.2 allows remote attackers to execute arbitrary PHP code via a URL in the spaw_root parameter.  NOTE: CVE analysis suggests that this issue is actually in a third party product, SPAW Editor PHP Edition, so this issue is probably a duplicate of CVE-2006-4656.

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

## Which versions are affected by CVE-2006-5291?

It affects 1 product.


Products: Alex Downloadengine.

## How do I fix CVE-2006-5291?

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

## Is CVE-2006-5291 being exploited?

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

Public exploit code:

- SL_Site 1.0 - 'spaw_root' Remote File Inclusion (exploitdb)
- Download-Engine 1.4.2 - 'spaw' Remote File Inclusion (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-5459](https://insights.sbomify.com/CVE-2006-5459/): File upload in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-5291 and fix it if it is affected.

What it is: CVE-2006-5291 is a high-severity code injection vulnerability in n/a, published on 16 Oct 2006. 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-2006-5291 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-2006-5291/ (Markdown: https://insights.sbomify.com/CVE-2006-5291/index.md)
```

## Sources

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

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