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

> Remote attackers can execute arbitrary code by including malicious files via the vwar_root2 parameter in the VWar Account module.

- **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:** 4 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q5h5-q6xv-vq45

## What is CVE-2006-1602?

CVE-2006-1602 is a high-severity vulnerability in n/a, published on 4 Apr 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 includes/functions_common.php in the VWar Account module (vWar_Account) in PHPNuke Clan 3.0.1 allows remote attackers to include arbitrary files via a URL in the vwar_root2 parameter.  NOTE: it is possible that this issue stems from a problem in VWar itself, but this is not clear.

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

It affects 1 product.


Products: Phpnuke-Clan Phpnuke-Clan.

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

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

## Is CVE-2006-1602 being exploited?

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

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

What it is: CVE-2006-1602 is a high-severity vulnerability in n/a, published on 4 Apr 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-1602 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-2006-1602/ (Markdown: https://insights.sbomify.com/CVE-2006-1602/index.md)
```

## Sources

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

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