# CVE-2006-0702: Path traversal in n/a

> Remote attackers with admin access can upload arbitrary files via path traversal in imageVue, potentially leading to code execution.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hx74-56pv-vfr2

## What is CVE-2006-0702?

CVE-2006-0702 is a medium-severity path traversal vulnerability in n/a, published on 15 Feb 2006. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

admin/upload.php in imageVue 16.1 allows remote attackers to upload arbitrary files to certain allowed folders via .. (dot dot) sequences in the path parameter.  NOTE: due to the lack of details, the specific vulnerability type cannot be determined, although it might be due to directory traversal.

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

It affects 1 product.


Products: Imagevue Imagevue.

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

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

## Is CVE-2006-0702 being exploited?

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

Public exploit code:

- ImageVue 0.16.1 - 'upload.php' Unrestricted Arbitrary File Upload (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-0700](https://insights.sbomify.com/CVE-2006-0700/): Information disclosure in n/a (medium 5.0)
- [CVE-2006-0701](https://insights.sbomify.com/CVE-2006-0701/): Path traversal in n/a (medium 5.0)
- [CVE-2008-1273](https://insights.sbomify.com/CVE-2008-1273/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2006-0703](https://insights.sbomify.com/CVE-2006-0703/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0702 is a medium-severity path traversal vulnerability in n/a, published on 15 Feb 2006. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-0702 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-0702/ (Markdown: https://insights.sbomify.com/CVE-2006-0702/index.md)
```

## Sources

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

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