# CVE-2018-21096: Cross-site request forgery in n/a

> Attackers can perform unauthorized actions on NETGEAR wireless access points via CSRF, requiring firmware upgrades to mitigate.

- **Severity:** Medium 5.2 (`CVSS:3.0/AC:L/AV:A/A:H/C:N/I:N/PR:L/S:U/UI:R`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Apr 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9rj5-qrrr-fwj9

## What is CVE-2018-21096?

CVE-2018-21096 is a medium-severity vulnerability in n/a, published on 27 Apr 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Certain NETGEAR devices are affected by CSRF. This affects WAC120 before 2.1.7, WAC505 before 5.0.5.4, WAC510 before 5.0.5.4, WNAP320 before 3.7.11.4, WNAP210v2 before 3.7.11.4, WNDAP350 before 3.7.11.4, WNDAP360 before 3.7.11.4, WNDAP660 before 3.7.11.4, WNDAP620 before 2.1.7, WND930 before 2.1.5, and WN604 before 3.3.10.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 11 products.


Products: Netgear Wac120 Firmware, Netgear Wac505 Firmware, Netgear Wac510 Firmware, Netgear Wn604 Firmware, Netgear Wnap210 Firmware, Netgear Wnap320 Firmware, Netgear Wnd930 Firmware, Netgear Wndap350 Firmware, Netgear Wndap360 Firmware, Netgear Wndap620 Firmware, Netgear Wndap660 Firmware.

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

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

## Is CVE-2018-21096 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-21094](https://insights.sbomify.com/CVE-2018-21094/): Misconfiguration in n/a (high 7.3)
- [CVE-2017-18863](https://insights.sbomify.com/CVE-2017-18863/): Command injection in n/a (high 7.1)
- [CVE-2018-21097](https://insights.sbomify.com/CVE-2018-21097/): Memory corruption in n/a (high 7.1)
- [CVE-2017-18805](https://insights.sbomify.com/CVE-2017-18805/): Command injection in n/a (medium 6.7)
- [CVE-2017-18806](https://insights.sbomify.com/CVE-2017-18806/): Command injection in n/a (medium 6.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-21096 is a medium-severity vulnerability in n/a, published on 27 Apr 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-21096 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-2018-21096/ (Markdown: https://insights.sbomify.com/CVE-2018-21096/index.md)
```

## Sources

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

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