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

> Remote attackers can inject arbitrary web script via the admin interface, 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:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5vf4-cxj2-f4wr

## What is CVE-2006-3929?

CVE-2006-3929 is a medium-severity cross-site scripting vulnerability in n/a, published on 31 Jul 2006. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Cross-site scripting (XSS) vulnerability in the Forms/rpSysAdmin script on the Zyxel Prestige 660H-61 ADSL Router running firmware 3.40(PT.0)b32 allows remote attackers to inject arbitrary web script or HTML via hex-encoded values in the a parameter.

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

It affects 1 product.


Products: Zyxel Prestige 660h-61.

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

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

## Is CVE-2006-3929 being exploited?

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

Public exploit code:

- ZYXEL Prestige 660H-61 ADSL Router - Cross-Site Scripting (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-3929 is a medium-severity cross-site scripting vulnerability in n/a, published on 31 Jul 2006. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-3929 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-3929/ (Markdown: https://insights.sbomify.com/CVE-2006-3929/index.md)
```

## Sources

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

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