# CVE-2005-3764: File upload in n/a

> Attackers can upload malicious files with spoofed MIME types in the image gallery, potentially leading to code execution or HTML injection.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Nov 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6r8p-cw9m-43r8

## What is CVE-2005-3764?

CVE-2005-3764 is a critical vulnerability in n/a, published on 22 Nov 2005. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The image gallery (imagegallery) component in Exponent CMS 0.96.3 and later versions does not properly check the MIME type of uploaded files, with unknown impact from the preview icon, possibly involving injection of HTML.

## Which versions are affected by CVE-2005-3764?

It affects 1 product.


Products: Exponent Exponent.

## How do I fix CVE-2005-3764?

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

## Is CVE-2005-3764 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-3762](https://insights.sbomify.com/CVE-2005-3762/): SQL injection in n/a (high 7.5)
- [CVE-2005-3765](https://insights.sbomify.com/CVE-2005-3765/): File upload in n/a (high 7.5)
- [CVE-2005-3763](https://insights.sbomify.com/CVE-2005-3763/): Information disclosure in n/a (medium 5.0)
- [CVE-2005-3766](https://insights.sbomify.com/CVE-2005-3766/): Missing authorization in n/a (medium 5.0)
- [CVE-2005-3767](https://insights.sbomify.com/CVE-2005-3767/): File upload in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-3764 and fix it if it is affected.

What it is: CVE-2005-3764 is a critical vulnerability in n/a, published on 22 Nov 2005. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2005-3764 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-2005-3764/ (Markdown: https://insights.sbomify.com/CVE-2005-3764/index.md)
```

## Sources

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

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