# CVE-2006-1584: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML into the Warcraft III Replay Parser for PHP, potentially compromising user sessions.

- **Severity:** Medium 6.4 (`AV:N/AC:L/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:** 2 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9rhj-9346-f3g5

## What is CVE-2006-1584?

CVE-2006-1584 is a medium-severity cross-site scripting vulnerability in n/a, published on 2 Apr 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in index.php in Warcraft III Replay Parser for PHP 1.8c allows remote attackers to inject arbitrary web script or HTML via the page parameter, possibly related to fopen function calls or file uploads.  NOTE: post-disclosure analysis by CVE suggests that the "page" parameter is not used in this product, and "id" might be the affected parameter.

## Which versions are affected by CVE-2006-1584?

It affects 1 product.


Products: Juliusz Julas Gonera Warcraft Iii Replay Parser Php.

## How do I fix CVE-2006-1584?

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

## Is CVE-2006-1584 being exploited?

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

Public exploit code:

- Warcraft III Replay Parser for PHP 1.8.c - 'index.php' Remote File Inclusion (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-1583](https://insights.sbomify.com/CVE-2006-1583/): Cross-site scripting in n/a (medium 5.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-1584 and fix it if it is affected.

What it is: CVE-2006-1584 is a medium-severity cross-site scripting vulnerability in n/a, published on 2 Apr 2006. 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-2006-1584 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-2006-1584/ (Markdown: https://insights.sbomify.com/CVE-2006-1584/index.md)
```

## Sources

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

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