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

> Remote attackers can execute arbitrary code via directory traversal in the uname parameter of profile.php in TinyPHPforum.

- **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:** 24 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8hr7-64p4-q5x4

## What is CVE-2006-7063?

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

### Official description

Directory traversal vulnerability in profile.php in TinyPHPforum 3.6 and earlier allows remote attackers to include and execute arbitrary files via ".." sequences in the uname parameter.

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

It affects 1 product.


Products: Tinyphpforum Tinyphpforum.

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

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

## Is CVE-2006-7063 being exploited?

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

Public exploit code:

- TinyPHP Forum 3.6 - 'profile.php' Remote Code Execution (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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