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

> Remote attackers can inject arbitrary web script via multiple input fields in Dragon's Kingdom Script, potentially leading to session hijacking or malicious actions.

- **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:** No
- **Published:** 13 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pf33-g3xv-r9v8

## What is CVE-2006-3539?

CVE-2006-3539 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 Jul 2006. 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 DKScript.com Dragon's Kingdom Script 1.0 allow remote attackers to inject arbitrary web script or HTML via a javascript URI in the SRC attribute of an IMG element in the (1) Subject and (2) Message fields in a do=write (aka Send Mail Message) action in gamemail.php; the (3) Gender, (4) Country/Location, (5) MSN Messenger, (6) AOL Instant Messenger, (7) Yahoo Instant Messenger, and (8) ICQ fields in a do=onlinechar (aka Edit your Profile) action in index.php, as accessed by dk.php; a javascript URI in the SRC attribute of an IMG element in the (9) Title and (10) Message fields in a do=new (aka Create Thread) action in general.php; and a javascript URI in the SRC attribute of an IMG element in unspecified fields in (11) other Forum posts and (12) Forum replies.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Dkscript Dragons Kingdom Script.

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

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

## Is CVE-2006-3539 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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