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

> Remote attackers can execute cross-site scripting attacks and access sensitive user and database information via direct requests to the application.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Nov 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-9wwc-xv4f-3h57

## What is CVE-2004-2563?

CVE-2004-2563 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Serena TeamTrack 6.1.1 allows remote attackers to obtain sensitive information such as user names, versions, and database information, and conduct cross-site scripting (XSS) attacks, via a direct request to tmtrack.dll with modified LoginPage and Template parameters.

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

It affects 1 product.


Products: Serena Software Serena Teamtrack.

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

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

## Is CVE-2004-2563 being exploited?

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

Public exploit code:

- Serena TeamTrack 6.1.1 - Remote Authentication Bypass (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-2563 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-2563 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-2563/ (Markdown: https://insights.sbomify.com/CVE-2004-2563/index.md)
```

## Sources

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

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