# CVE-2004-2700: File upload in n/a

> Remote authenticated administrators can upload arbitrary executable files, leading to potential code execution on the server.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2007
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-7348-84cp-xjx4

## What is CVE-2004-2700?

CVE-2004-2700 is a critical vulnerability in n/a, published on 6 Oct 2007. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in AspDotNetStorefront 3.3 allows remote authenticated administrators to upload arbitrary files with executable extensions via admin/images.aspx.

Weakness: CWE-264

## Which versions are affected by CVE-2004-2700?

It affects 1 product.


Products: Aspdotnetstorefront Aspdotnetstorefront.

## How do I fix CVE-2004-2700?

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

## Is CVE-2004-2700 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-2699](https://insights.sbomify.com/CVE-2004-2699/): Missing authorization in n/a (medium 4.3)
- [CVE-2004-2701](https://insights.sbomify.com/CVE-2004-2701/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2700 and fix it if it is affected.

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

## Sources

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

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