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

> Remote attackers can execute arbitrary code via path traversal in Quick.Cart when specific PHP configurations are enabled.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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-g378-596r-589f

## What is CVE-2006-6390?

CVE-2006-6390 is a medium-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

Multiple directory traversal vulnerabilities in Open Solution Quick.Cart 2.0, when register_globals is enabled and magic_quotes_gpc is disabled, allow remote attackers to include and execute arbitrary local files via a .. (dot dot) in the config[db_type] parameter to (1) categories.php, (2) couriers.php, (3) orders.php, and (4) products.php in actions_admin/; and (5) orders.php and (6) products.php in actions_client/; as demonstrated by injecting PHP sequences into an Apache HTTP Server log file, which is then included by one of these PHP scripts.

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

It affects 1 product.


Products: Open Solution Quick.cart.

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

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

## Is CVE-2006-6390 being exploited?

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

Public exploit code:

- QuickCart 2.0 - 'categories.php' Local File Inclusion (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-3138](https://insights.sbomify.com/CVE-2007-3138/): Path traversal in n/a (high 7.5)
- [CVE-2007-1407](https://insights.sbomify.com/CVE-2007-1407/): Unspecified vulnerability in OpenSolution Quick.Cart before 2.1 has unknown impact and attack vectors, related to a "low critical exploit." (high 7.5)
- [CVE-2005-1588](https://insights.sbomify.com/CVE-2005-1588/): SQL injection in n/a (high 7.5)
- [CVE-2007-3139](https://insights.sbomify.com/CVE-2007-3139/): Hardcoded credentials in n/a (medium 6.8)
- [CVE-2006-6391](https://insights.sbomify.com/CVE-2006-6391/): Path traversal in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6390 is a medium-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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-6390 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-6390/ (Markdown: https://insights.sbomify.com/CVE-2006-6390/index.md)
```

## Sources

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

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