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

> Remote attackers can exploit a directory traversal flaw in plx Pay to execute arbitrary local files or steal sensitive user credentials.

- **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:** 8 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qv83-4x5r-c2c6

## What is CVE-2006-6392?

CVE-2006-6392 is a high-severity path traversal vulnerability in n/a, published on 8 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 index.php in plx Web Studio (aka plxWebDev) plx Pay 3.2 and earlier allows remote attackers to include and execute arbitrary local files, or obtain user credentials and other sensitive information, via a .. (dot dot) in the read parameter. NOTE: The provenance of this information is unknown; the details are obtained solely from third party information.

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

It affects 1 product.


Products: Plx Web Studio Plx Pay.

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

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

## Is CVE-2006-6392 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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