# CVE-2006-6463: File upload in n/a

> Authenticated administrators can upload arbitrary PHP files to the web root, enabling remote code execution on the Midicart e-commerce platform.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mw55-8v3w-mgmh

## What is CVE-2006-6463?

CVE-2006-6463 is a medium-severity vulnerability in n/a, published on 11 Dec 2006. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in admin/add.php in Midicart allows remote authenticated users to upload arbitrary .php files, and possibly other files, to the images/ directory under the web root.

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

It affects 1 product.


Products: Midicart Software Midicart Php Shopping Cart.

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

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

## Is CVE-2006-6463 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-2601](https://insights.sbomify.com/CVE-2005-2601/): SQL injection in n/a (high 7.5)
- [CVE-2005-1501](https://insights.sbomify.com/CVE-2005-1501/): Information disclosure in n/a (high 7.5)
- [CVE-2005-1502](https://insights.sbomify.com/CVE-2005-1502/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2006-6464](https://insights.sbomify.com/CVE-2006-6464/): Business logic in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6463 is a medium-severity vulnerability in n/a, published on 11 Dec 2006. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-6463 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-6463/ (Markdown: https://insights.sbomify.com/CVE-2006-6463/index.md)
```

## Sources

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

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