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

> Remote attackers can steal authentication cookies via XSS in Express-Web CMS parameters and headers, potentially leading to account takeover.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **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:** 10 Jul 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6346-5chp-6r3x

## What is CVE-2004-2210?

CVE-2004-2210 is a medium-severity cross-site scripting vulnerability in n/a, published on 10 Jul 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

Multiple cross-site scripting (XSS) vulnerabilities in Express-Web Content Management System (CMS) allow remote attackers to steal cookie-based authentication information and possibly perform other exploits via the (1) n, (2) b, (3) e, or (4) a parameters to default.asp, (5) the Referer header in an HTTP request to login.asp, or (6) the email parameter to subscribe/default.asp.

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

It affects 1 product.


Products: Express-Web Express-Web Content Management System.

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

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

## Is CVE-2004-2210 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2004-2210 is a medium-severity cross-site scripting vulnerability in n/a, published on 10 Jul 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: There is no known exploitation of CVE-2004-2210 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-2210/ (Markdown: https://insights.sbomify.com/CVE-2004-2210/index.md)
```

## Sources

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

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