# CVE-2021-32122: Cross-site request forgery in n/a

> Attackers can perform unauthorized actions on NETGEAR WiFi extenders by tricking users into visiting malicious sites.

- **Severity:** Critical 9.8 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-37f4-hx4j-c54c

## What is CVE-2021-32122?

CVE-2021-32122 is a critical vulnerability in n/a, published on 10 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Certain NETGEAR devices are affected by CSRF. This affects EX3700 before 1.0.0.90, EX3800 before 1.0.0.90, EX6120 before 1.0.0.64, and EX6130 before 1.0.0.44.

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

## Which versions are affected by CVE-2021-32122?

It affects 4 products.


Products: Netgear Ex3700 Firmware, Netgear Ex3800 Firmware, Netgear Ex6120 Firmware, Netgear Ex6130 Firmware.

## How do I fix CVE-2021-32122?

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

## Is CVE-2021-32122 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-18747](https://insights.sbomify.com/CVE-2017-18747/): Misconfiguration in n/a (high 8.8)
- [CVE-2017-18752](https://insights.sbomify.com/CVE-2017-18752/): Path traversal in n/a (high 8.8)
- [CVE-2017-18772](https://insights.sbomify.com/CVE-2017-18772/): Auth bypass in n/a (high 8.8)
- [CVE-2025-5934](https://insights.sbomify.com/CVE-2025-5934/): Netgear EX3700 mtd sub_41619C stack-based overflow (high 8.7)
- [CVE-2024-35519](https://insights.sbomify.com/CVE-2024-35519/): Command injection in n/a (high 8.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-32122 and fix it if it is affected.

What it is: CVE-2021-32122 is a critical vulnerability in n/a, published on 10 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-32122 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-2021-32122/ (Markdown: https://insights.sbomify.com/CVE-2021-32122/index.md)
```

## Sources

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

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