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

> Remote attackers can execute arbitrary scripts by uploading malicious files via the avatar upload feature in OpenBB.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 10 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-vjgj-h698-pm55

## What is CVE-2004-1969?

CVE-2004-1969 is a high-severity vulnerability in n/a, published on 10 May 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The avatar upload capability in Open Bulletin Board (OpenBB) 1.0.6 and earlier allows remote attackers to execute arbitrary script by uploading files that include scripting code such as Javascript.

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


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

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

## Is CVE-2004-1969 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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