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

> Remote attackers can execute arbitrary PHP code in WonderEdit Pro CMS via a remote file inclusion vulnerability in user_bottom.php.

- **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:** 7 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-83mp-mpcx-w8ph

## What is CVE-2006-3422?

CVE-2006-3422 is a high-severity vulnerability in n/a, published on 7 Jul 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 WonderEdit Pro CMS allows remote attackers to execute arbitrary PHP code via the config[template_path] parameter in user_bottom.php, as used by multiple templates including (1) rwb (template/rwb/user_bottom.php), (2) gwb (template/rwb/user_bottom.php, (3) blues, (4) bluwhi, and (5) grns.

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

It affects 1 product.


Products: Wonderedit Wonderedit Pro Cms.

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

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

## Is CVE-2006-3422 being exploited?

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

Public exploit code:

- WonderEdit Pro CMS (template_path) - Remote File Inclusion (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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