# CVE-2019-20752: Cross-site scripting in n/a

> Stored XSS in NETGEAR routers allows attackers to inject scripts, potentially leading to session hijacking or malicious actions.

- **Severity:** Medium 4.8 (`CVSS:3.0/AC:L/AV:N/A:N/C:L/I:L/PR:H/S:C/UI:R`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Apr 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cvq9-v475-8x82

## What is CVE-2019-20752?

CVE-2019-20752 is a medium-severity cross-site scripting vulnerability in Netgear D3600 Firmware, published on 16 Apr 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Certain NETGEAR devices are affected by stored XSS. This affects D3600 before 1.0.0.75, D6000 before 1.0.0.75, D7800 before 1.0.1.44, DM200 before 1.0.0.58, R7800 before 1.0.2.58, R8900 before 1.0.4.12, R9000 before 1.0.4.12, RBK20 before 2.3.0.28, RBR20 before 2.3.0.28, RBS20 before 2.3.0.28, RBK40 before 2.3.0.28, RBS40 before 2.3.0.28, RBK50 before 2.3.0.32, RBR50 before 2.3.0.32, RBS50 before 2.3.0.32, WN3000RPv2 before 1.0.0.68, WN3000RPv3 before 1.0.2.70, WN3100RPv2 before 1.0.0.60, WNDR4300v2 before 1.0.0.58, WNDR4500v3 before 1.0.0.58, and WNR2000v5 before 1.0.0.68.

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

## Which versions are affected by CVE-2019-20752?

It affects 20 products.


Products: Netgear D3600 Firmware, Netgear D6000 Firmware, Netgear D7800 Firmware, Netgear Dm200 Firmware, Netgear R7800 Firmware, Netgear R8900 Firmware, Netgear R9000 Firmware, Netgear Rbk20 Firmware, Netgear Rbk40 Firmware, Netgear Rbk50 Firmware, Netgear Rbr20 Firmware, Netgear Rbr50 Firmware, Netgear Rbs20 Firmware, Netgear Rbs40 Firmware, Netgear Rbs50 Firmware, Netgear Wn3000rp Firmware, Netgear Wn3100rp Firmware, Netgear Wndr4300 Firmware, Netgear Wndr4500 Firmware, Netgear Wnr2000 Firmware.

## How do I fix CVE-2019-20752?

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

## Is CVE-2019-20752 being exploited?

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

## Other vulnerabilities in Netgear D3600 Firmware

- [CVE-2020-35799](https://insights.sbomify.com/CVE-2020-35799/): Memory corruption in n/a (high 8.8)
- [CVE-2018-21207](https://insights.sbomify.com/CVE-2018-21207/): Memory corruption in n/a (high 8.8)
- [CVE-2018-21210](https://insights.sbomify.com/CVE-2018-21210/): Memory corruption in n/a (high 8.8)
- [CVE-2018-21211](https://insights.sbomify.com/CVE-2018-21211/): Memory corruption in n/a (high 8.8)
- [CVE-2018-21212](https://insights.sbomify.com/CVE-2018-21212/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-20752 and fix it if it is affected.

What it is: CVE-2019-20752 is a medium-severity cross-site scripting vulnerability in Netgear D3600 Firmware, published on 16 Apr 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-20752 in the wild and no public exploit code.

Affected product: Netgear D3600 Firmware. 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-2019-20752/ (Markdown: https://insights.sbomify.com/CVE-2019-20752/index.md)
```

## Sources

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

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