# CVE-2007-2289: File upload in n/a

> Authenticated attackers can execute arbitrary PHP code via remote file inclusion in the Download Engine admin panel.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 26 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h2gj-j3wh-6965

## What is CVE-2007-2289?

CVE-2007-2289 is a high-severity vulnerability in n/a, published on 26 Apr 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PHP remote file inclusion vulnerability in admin/includes/spaw/dialogs/insert_link.php in download engine (Download-Engine) 1.4.1 allows remote authenticated users to execute arbitrary PHP code via a URL in the spaw_root parameter, a different vector than CVE-2007-2255.  NOTE: this may be an issue in SPAW.

## Which versions are affected by CVE-2007-2289?

It affects 1 product.


Products: Alexscriptengine Download-Engine.

## How do I fix CVE-2007-2289?

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

## Is CVE-2007-2289 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-2255](https://insights.sbomify.com/CVE-2007-2255/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2289 and fix it if it is affected.

What it is: CVE-2007-2289 is a high-severity vulnerability in n/a, published on 26 Apr 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-2289 in the wild and no public exploit code.

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-2007-2289/ (Markdown: https://insights.sbomify.com/CVE-2007-2289/index.md)
```

## Sources

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

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