# CVE-2016-11055: Cross-site request forgery in n/a

> Attackers can perform unauthorized actions on NETGEAR devices via CSRF, requiring users to visit malicious sites.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Apr 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-rxh2-hx5f-x65g

## What is CVE-2016-11055?

CVE-2016-11055 is a medium-severity vulnerability in n/a, published on 28 Apr 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Certain NETGEAR devices are affected by CSRF. This affects CM400 before 2017-01-11, CM600 before 2017-01-11, D1500 before 2017-01-11, D500 before 2017-01-11, DST6501 before 2017-01-11, JNR1010v1 before 2017-01-11, JWNR2000Tv3 before 2017-01-11, JWNR2010v3 before 2017-01-11, PLW1000 before 2017-01-11, PLW1010 before 2017-01-11, WNR500 before 2017-01-11, WNR612v3 before 2017-01-11, N450 before 2017-01-11, and CG3000Dv2 before 2017-01-11.

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

## Which versions are affected by CVE-2016-11055?

It affects 13 products.


Products: Netgear Cm400 Firmware, Netgear Cm600 Firmware, Netgear D1500 Firmware, Netgear D500 Firmware, Netgear Dst6501 Firmware, Netgear Jnr1010 Firmware, Netgear Jwnr2000t Firmware, Netgear Jwnr2010 Firmware, Netgear N450 Cg3000d Firmware, Netgear Plw1000 Firmware, Netgear Plw1010 Firmware, Netgear Wnr500 Firmware, Netgear Wnr612 Firmware.

## How do I fix CVE-2016-11055?

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

## Is CVE-2016-11055 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-11055 and fix it if it is affected.

What it is: CVE-2016-11055 is a medium-severity vulnerability in n/a, published on 28 Apr 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-11055 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-2016-11055/ (Markdown: https://insights.sbomify.com/CVE-2016-11055/index.md)
```

## Sources

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

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