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

> Remote attackers with admin privileges can upload and execute arbitrary files due to improper filename validation in the image gallery application.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/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:** 12 Feb 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-rgvv-2cqq-qhg4

## What is CVE-2004-1408?

CVE-2004-1408 is a high-severity vulnerability in n/a, published on 12 Feb 2005. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The addImage method for admin.class.php in Image Gallery Web Application 0.9.10 does not properly check filenames, which allows remote attackers to upload and execute arbitrary files.

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


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

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

## Is CVE-2004-1408 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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