# CVE-2004-2625: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML via malicious IMG tags in Outblaze Email, requiring user interaction to execute.

- **Severity:** Medium 5.1 (`AV:N/AC:H/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Dec 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-j959-4486-mmwm

## What is CVE-2004-2625?

CVE-2004-2625 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Dec 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting (XSS) vulnerability in Outblaze Email allows remote attackers to inject arbitrary web script or HTML via Javascript in an attribute of an IMG tag.

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

It affects 1 product.


Products: Outblaze Outblaze Email.

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

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

## Is CVE-2004-2625 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-2625 exists.

Public exploit code:

- Outblaze Webmail - HTML Injection (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-2625 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Dec 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-2625 exists.

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-2625/ (Markdown: https://insights.sbomify.com/CVE-2004-2625/index.md)
```

## Sources

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

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