# CVE-2013-3069: Cross-site scripting in n/a

> Authenticated attackers can inject scripts into NETGEAR WNDR4700 router interfaces, potentially compromising user sessions.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/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:** 25 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7p6q-wh2x-4x7c

## What is CVE-2013-3069?

CVE-2013-3069 is a low-severity cross-site scripting vulnerability in n/a, published on 25 Apr 2014. 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 NETGEAR WNDR4700 with firmware 1.0.0.34 allow remote authenticated users to inject arbitrary web script or HTML via the (1) UserName or (2) Password to the NAS User Setup page, (3) deviceName to USB_advanced.htm, or (4) Network Key to the Wireless Setup page.

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

## Which versions are affected by CVE-2013-3069?

It affects 2 products.


Products: Netgear Wndr4700, Netgear Wndr4700 Firmware.

## How do I fix CVE-2013-3069?

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

## Is CVE-2013-3069 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-3069 and fix it if it is affected.

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

## Sources

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

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