# CVE-2021-20860: Cross-site request forgery in ELECOM LAN routers

> Remote authenticated attackers can hijack administrator sessions via CSRF, potentially gaining full control of ELECOM LAN routers.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 1 Dec 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-g5f2-2vwc-fg5m

## What is CVE-2021-20860?

CVE-2021-20860 is a high-severity vulnerability in ELECOM LAN routers, published on 1 Dec 2021. 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

Cross-site request forgery (CSRF) vulnerability in ELECOM LAN routers (WRC-1167GST2 firmware v1.25 and prior, WRC-1167GST2A firmware v1.25 and prior, WRC-1167GST2H firmware v1.25 and prior, WRC-2533GS2-B firmware v1.52 and prior, WRC-2533GS2-W firmware v1.52 and prior, WRC-1750GS firmware v1.03 and prior, WRC-1750GSV firmware v2.11 and prior, WRC-1900GST firmware v1.03 and prior, WRC-2533GST firmware v1.03 and prior, WRC-2533GSTA firmware v1.03 and prior, WRC-2533GST2 firmware v1.25 and prior, WRC-2533GST2SP firmware v1.25 and prior, WRC-2533GST2-G firmware v1.25 and prior, and EDWRC-2533GST2 firmware v1.25 and prior) allows a remote authenticated attacker to hijack the authentication of an administrator via a specially crafted page.

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

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

It affects 14 products.


Products: Elecom Edwrc-2533gst2 Firmware, Elecom Wrc-1167gst2 Firmware, Elecom Wrc-1167gst2a Firmware, Elecom Wrc-1167gst2h Firmware, Elecom Wrc-1750gs Firmware, Elecom Wrc-1750gsv Firmware, Elecom Wrc-1900gst Firmware, Elecom Wrc-2533gs2-B Firmware, Elecom Wrc-2533gs2-W Firmware, Elecom Wrc-2533gst2-G Firmware, Elecom Wrc-2533gst2 Firmware, Elecom Wrc-2533gst2sp Firmware, Elecom Wrc-2533gst Firmware, Elecom Wrc-2533gsta Firmware.

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

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

## Is CVE-2021-20860 being exploited?

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

## Other vulnerabilities in ELECOM LAN routers

- [CVE-2022-25915](https://insights.sbomify.com/CVE-2022-25915/): Auth bypass in ELECOM LAN routers (high 8.8)
- [CVE-2021-20861](https://insights.sbomify.com/CVE-2021-20861/): Auth bypass in ELECOM LAN routers (high 8.8)
- [CVE-2021-20864](https://insights.sbomify.com/CVE-2021-20864/): Auth bypass in ELECOM routers (high 8.8)
- [CVE-2021-20859](https://insights.sbomify.com/CVE-2021-20859/): Command injection in ELECOM LAN routers (high 8.0)
- [CVE-2021-20863](https://insights.sbomify.com/CVE-2021-20863/): Command injection in ELECOM routers (high 8.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-20860 is a high-severity vulnerability in ELECOM LAN routers, published on 1 Dec 2021. 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-2021-20860 in the wild and no public exploit code.

Affected product: ELECOM LAN routers. 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-20860/ (Markdown: https://insights.sbomify.com/CVE-2021-20860/index.md)
```

## Sources

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

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