# CVE-2007-6676: File upload in n/a

> Remote attackers can upload dangerous file types like HTML or ASP due to default configuration, potentially leading to code execution.

- **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:** 8 Jan 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8989-95x5-m92c

## What is CVE-2007-6676?

CVE-2007-6676 is a medium-severity vulnerability in n/a, published on 8 Jan 2008. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The default configuration of Uber Uploader (UU) 5.3.6 and earlier does not block uploads of (1) .html, (2) .asp, and other possibly dangerous extensions, which allows remote attackers to use these extensions in uploads via (a) uu_file_upload.php, related to uu_file_upload.js and (b) uber_uploader_file.php, related to uber_uploader_file.js, a different issue than CVE-2007-0123.  NOTE: the vendor disputes the severity of the issue, noting that it is the administrator's responsibility to "add file extensions that you may or may not want uploaded."

Weakness: CWE-16

## Which versions are affected by CVE-2007-6676?

It affects 1 product.


Products: Uber Uploader Uber Uploader.

## How do I fix CVE-2007-6676?

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

## Is CVE-2007-6676 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-0123](https://insights.sbomify.com/CVE-2007-0123/): File upload in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-6676 and fix it if it is affected.

What it is: CVE-2007-6676 is a medium-severity vulnerability in n/a, published on 8 Jan 2008. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-6676 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-2007-6676/ (Markdown: https://insights.sbomify.com/CVE-2007-6676/index.md)
```

## Sources

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

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