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

> Remote attackers can read arbitrary files and potentially execute code via directory traversal in the template parameter of 4Images.

- **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:** 27 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-796x-phgf-g22f

## What is CVE-2006-0899?

CVE-2006-0899 is a high-severity path traversal vulnerability in n/a, published on 27 Feb 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in index.php in 4Images 1.7.1 and earlier allows remote attackers to read and include arbitrary files via ".." (dot dot) sequences in the template parameter.

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

It affects 1 product.


Products: 4images Image Gallery Management System.

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

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

## Is CVE-2006-0899 being exploited?

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

Public exploit code:

- 4Images 1.7.1 - Local File Inclusion / Remote Code Execution (exploitdb)

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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