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

> Remote attackers can read arbitrary files via directory traversal in phpXplorer, though impact is limited by existing file upload capabilities.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cfr7-m7j6-q7hh

## What is CVE-2006-0244?

CVE-2006-0244 is a medium-severity path traversal vulnerability in n/a, published on 18 Jan 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in workspaces.php in phpXplorer 0.9.33 allows remote attackers to include arbitrary files via a .. (dot dot) and trailing null byte (%00) in the sShare parameter.  NOTE: a followup post claims that this is not a vulnerability since the functionality of phpXplorer supports the upload of PHP files, which would not cross privilege boundaries since the PHP functionality would support read access outside the web root

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

It affects 1 product.


Products: Phpxplorer Phpxplorer.

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

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

## Is CVE-2006-0244 being exploited?

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

Public exploit code:

- PHPXplorer 0.9.33 - 'Workspaces.php' Directory Traversal (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-0434](https://insights.sbomify.com/CVE-2006-0434/): Path traversal in n/a (medium 5.0)
- [CVE-2005-4301](https://insights.sbomify.com/CVE-2005-4301/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0244 is a medium-severity path traversal vulnerability in n/a, published on 18 Jan 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-0244 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-0244/ (Markdown: https://insights.sbomify.com/CVE-2006-0244/index.md)
```

## Sources

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

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