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

> Remote attackers can create arbitrary empty files on the server via directory traversal in the orig_id parameter of MBoard.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-prrf-57xv-6pwh

## What is CVE-2006-6262?

CVE-2006-6262 is a medium-severity path traversal vulnerability in n/a, published on 4 Dec 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in mboard.php in PHPJunkYard (aka Klemen Stirn) MBoard 1.22 and earlier allows remote attackers to create arbitrary empty files via a .. (dot dot) in the orig_id parameter.

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

It affects 1 product.


Products: Phpjunkyard Phpjunkyard Mboard.

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

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

## Is CVE-2006-6262 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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