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

> Remote attackers can inject arbitrary scripts into WordPress via multiple parameters, requiring user interaction to execute malicious code.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 Feb 2005
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-1559, GHSA-w42r-hrg2-j8mr

## What is CVE-2004-1559?

CVE-2004-1559 is a medium-severity cross-site scripting vulnerability in Wordpress Wordpress, published on 20 Feb 2005. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in Wordpress 1.2 allow remote attackers to inject arbitrary web script or HTML via the (1) redirect_to, text, popupurl, or popuptitle parameters to wp-login.php, (2) redirect_url parameter to admin-header.php, (3) popuptitle, popupurl, content, or post_title parameters to bookmarklet.php, (4) cat_ID parameter to categories.php, (5) s parameter to edit.php, or (6) s or mode parameter to edit-comments.php.

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

It affects 1 product.


Products: Wordpress Wordpress.

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

Upgrade to a fixed version.

## Is CVE-2004-1559 being exploited?

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

Public exploit code:

- WordPress Core 1.2 - 'wp-login.php' Multiple Cross-Site Scripting Vulnerabilities (exploitdb)
- WordPress Core 1.2 - 'admin-header.php?redirect_url' Cross-Site Scripting (exploitdb)
- WordPress Core 1.2 - 'bookmarklet.php' Multiple Cross-Site Scripting Vulnerabilities (exploitdb)
- WordPress Core 1.2 - 'categories.php?cat_ID' Cross-Site Scripting (exploitdb)
- WordPress Core 1.2 - 'edit.php?s' Cross-Site Scripting (exploitdb)
- WordPress Core 1.2 - 'edit-comments.php' Multiple Cross-Site Scripting Vulnerabilities (exploitdb)

## Other vulnerabilities in Wordpress Wordpress

- [CVE-2026-63030](https://insights.sbomify.com/CVE-2026-63030/): WordPress Core Interpretation Conflict (critical 9.8, exploited in the wild)
- [CVE-2026-87902](https://insights.sbomify.com/CVE-2026-87902/): WordPress Core Remote File Inclusion (high 8.1, exploited in the wild)
- [CVE-2026-60137](https://insights.sbomify.com/CVE-2026-60137/): WordPress Core SQL Injection (medium 5.9, exploited in the wild)
- [CVE-2012-2399](https://insights.sbomify.com/CVE-2012-2399/): Cross-site scripting in n/a (critical 10.0)
- [CVE-2012-2400](https://insights.sbomify.com/CVE-2012-2400/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-1559 is a medium-severity cross-site scripting vulnerability in Wordpress Wordpress, published on 20 Feb 2005. Any signed-in user can exploit it over the network, 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-1559 exists.

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

## Sources

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

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