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

> Remote attackers can inject arbitrary web script or HTML via name or message parameters in SkyeBox, requiring user interaction to execute.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** CVE-2006-2596, GHSA-r9c5-8jj7-vm4j

## What is CVE-2006-2584?

CVE-2006-2584 is a medium-severity cross-site scripting vulnerability in n/a, published on 25 May 2006. It can be exploited over the network, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in post.php in SkyeBox 1.2.0 allow remote attackers to inject arbitrary web script or HTML via the (1) name or (2) message parameters.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information, although it was likely prompted by a vague announcement from a researcher who incorrectly referred to the product as "SkyeShoutbox."

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

It affects 1 product.


Products: Skyebox Skyebox.

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

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

## Is CVE-2006-2584 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2584 is a medium-severity cross-site scripting vulnerability in n/a, published on 25 May 2006. It can be exploited over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-2584 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-2006-2584/ (Markdown: https://insights.sbomify.com/CVE-2006-2584/index.md)
```

## Sources

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

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