# CVE-2006-5421: File upload in n/a

> Remote attackers can execute arbitrary PHP code by uploading a malicious avatar image and referencing it via the pathtoconfig parameter.

- **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:** 20 Oct 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hgwj-3m4h-rvqq

## What is CVE-2006-5421?

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

### Official description

WSN Forum 1.3.4 and earlier allows remote attackers to execute arbitrary PHP code via a modified pathname in the pathtoconfig parameter that points to an avatar image that contains PHP code, which is then accessed from prestart.php.  NOTE: this issue has been labeled remote file inclusion, but that label only applies to the attack, not the underlying vulnerability.

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

It affects 1 product.


Products: Wsn Forum Wsn Forum.

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

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

## Is CVE-2006-5421 being exploited?

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

Public exploit code:

- WSN Forum 1.3.4 - 'prestart.php' Remote Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-3916](https://insights.sbomify.com/CVE-2005-3916/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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