dbcve.org
Wrc 1167gst2 FirmwareOperating system · Elecom

CVE-2021-20860

HIGH · 8.8 CVSS v3.1 Published 2021-12-01
Fix available
A fix is available. Upgrade to after 2.11 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cross-site request forgery (CSRF) vulnerability in multiple ELECOM LAN router models allows a remote authenticated attacker to hijack administrator authentication via a specially crafted page. The attack exploits the router's web interface lacking proper CSRF token validation, enabling malicious requests to be executed in the context of an authenticated administrator session.

MitigationUpdate router firmware to versions beyond those specified (v1.25, v1.52, or v1.03 depending on model). Until firmware is available, consider implementing additional network segmentation or using browser-based CSRF protections.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wrc 1167gst2 FirmwareOperating system
Affected:<= 1.25
Wrc 1167gst2a FirmwareOperating system
Affected:<= 1.25
Wrc 1167gst2h FirmwareOperating system
Affected:<= 1.25
Wrc 2533gs2 B FirmwareOperating system
Affected:<= 1.52
Wrc 2533gs2 W FirmwareOperating system
Affected:<= 1.52
Wrc 1750gs FirmwareOperating system
Affected:<= 1.03
Wrc 1750gsv FirmwareOperating system
Affected:<= 2.11
Wrc 1900gst FirmwareOperating system
Affected:<= 1.03

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the router model
    Locate the model name on the router's physical label or packaging, or check the web administration interface header for the model designation (e.g., Wrc 1167gst2, Wrc 2533gs2 B)
    Affected if The model is one of: Wrc 1167gst2, Wrc 1167gst2a, Wrc 1167gst2h, Wrc 2533gs2 B, Wrc 2533gs2 W, Wrc 1750gs, Wrc 1750gsv, or Wrc 1900gst
  2. Check the installed firmware version
    Log into the router's web administration interface and navigate to the System or Status page to view the firmware version, or use the CLI command 'show version' if SSH/Telnet access is available
    Affected if The firmware version is at or below 1.25 for Wrc 1167gst2 variants, at or below 1.52 for Wrc 2533gs2 models, at or below 1.03 for Wrc 1750gs/Wrc 1900gst, or at or below 2.11 for Wrc 1750gsv
  3. Verify the web management interface is accessible
    Attempt to access the router's web interface by entering the router's IP address in a web browser; confirm the login page loads
    Affected if The web administration interface is reachable on the local network (typically at http://192.168.0.1 or similar) and accepts administrator credentials
  4. Confirm CSRF protection is absent
    Inspect the router's login page HTML source or monitor HTTP requests during an authenticated session; look for CSRF tokens in forms or headers. The vulnerability exists if forms submit without requiring a unique token per request
    Affected if The router's web interface processes configuration changes without requiring a unique, session-bound CSRF token in each request

You are affected if your router model matches one of the eight listed models AND your firmware version is at or below the specified limit AND the web management interface is accessible and lacks CSRF token validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 2.11
Interim mitigation

Update router firmware to versions beyond those specified (v1.25, v1.52, or v1.03 depending on model). Until firmware is available, consider implementing additional network segmentation or using browser-based CSRF protections.

Fix this in Wrc 1167gst2 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-20860 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-20860 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data