# CVE-2018-21167: 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:A/A:N/C:L/I:L/PR:H/S:C/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Apr 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qgh9-p249-ccvq

## What is CVE-2018-21167?

CVE-2018-21167 is a medium-severity cross-site scripting vulnerability in Netgear D6100 Firmware, published on 27 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Certain NETGEAR devices are affected by stored XSS. This affects D6100 before 1.0.0.57, DM200 before 1.0.0.50, EX2700 before 1.0.1.32, EX6100v2 before 1.0.1.70, EX6150v2 before 1.0.1.70, EX6200v2 before 1.0.1.62, EX6400 before 1.0.1.78, EX7300 before 1.0.1.78, EX8000 before 1.0.0.114, R6100 before 1.0.1.22, R7500 before 1.0.0.122, R7800 before 1.0.2.42, R8900 before 1.0.3.10, R9000 before 1.0.3.10, WN2000RPTv3 before 1.0.1.26, WN3000RPv3 before 1.0.2.66, WN3100RPv2 before 1.0.0.42, WNDR3700v4 before 1.0.2.96, WNDR4300 before 1.0.2.98, WNDR4300v2 before 1.0.0.54, WNDR4500v3 before 1.0.0.54, and WNR2000v5 before 1.0.0.64.

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

## Which versions are affected by CVE-2018-21167?

It affects 21 products.


Products: Netgear D6100 Firmware, Netgear Dm200 Firmware, Netgear Ex2700 Firmware, Netgear Ex6100 Firmware, Netgear Ex6150 Firmware, Netgear Ex6200 Firmware, Netgear Ex6400 Firmware, Netgear Ex7300 Firmware, Netgear Ex8000 Firmware, Netgear R6100 Firmware, Netgear R7500 Firmware, Netgear R7800 Firmware, Netgear R8900 Firmware, Netgear R9000 Firmware, Netgear Wn2000rpt Firmware, Netgear Wn3000rp Firmware, Netgear Wn3100rp Firmware, Netgear Wndr3700 Firmware, Netgear Wndr4300 Firmware, Netgear Wndr4500 Firmware and 1 more.

## How do I fix CVE-2018-21167?

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

## Is CVE-2018-21167 being exploited?

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

## Other vulnerabilities in Netgear D6100 Firmware

- [CVE-2016-10174](https://insights.sbomify.com/CVE-2016-10174/): NETGEAR WNR2000v5 Router Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2018-21208](https://insights.sbomify.com/CVE-2018-21208/): Command injection in n/a (high 8.8)
- [CVE-2017-18764](https://insights.sbomify.com/CVE-2017-18764/): Command injection in n/a (high 8.8)
- [CVE-2018-21113](https://insights.sbomify.com/CVE-2018-21113/): Command injection in n/a (high 8.8)
- [CVE-2017-18776](https://insights.sbomify.com/CVE-2017-18776/): Auth bypass in n/a (high 8.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-21167 and fix it if it is affected.

What it is: CVE-2018-21167 is a medium-severity cross-site scripting vulnerability in Netgear D6100 Firmware, published on 27 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-21167 in the wild and no public exploit code.

Affected product: Netgear D6100 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-2018-21167/ (Markdown: https://insights.sbomify.com/CVE-2018-21167/index.md)
```

## Sources

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

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