dbcve.org
Wrc 1167gs2 B FirmwareOperating system · Elecom

CVE-2024-23910

HIGH · 8.8 CVSS v3.1 Published 2024-02-28
Fix available
A fix is available. Upgrade to 1.27 / 1.31 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 wireless LAN routers and wireless LAN repeater allows a remote unauthenticated attacker to hijack the authentication of administrators and to perform unintended operations to the affected product. Note that WMC-X1800GST-B and WSC-X1800GS-B are also included in e-Mesh Starter Kit "WMC-2LX-B".

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 · moderate confidence

Cross-site request forgery (CSRF) vulnerability in ELECOM wireless LAN routers and repeaters (including WMC-X1800GST-B, WSC-X1800GS-B in WMC-2LX-B e-Mesh Starter Kit) allows remote unauthenticated attackers to hijack administrator sessions and perform unauthorized configuration changes.

MitigationContact ELECOM for available firmware updates that address this CSRF vulnerability; implement anti-CSRF tokens, SameSite cookie attributes, and Origin/Referer header validation as compensatory measures until official patch is available.

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 1167gs2 B FirmwareOperating system
Affected:< 1.73
Wrc 1167gs2h B FirmwareOperating system
Affected:< 1.73
Wrc 1167gst2 FirmwareOperating system
Affected:< 1.34
Wrc 2533gs2 B FirmwareOperating system
Affected:< 1.68
Wrc 2533gs2 W FirmwareOperating system
Affected:< 1.68
Wrc 2533gs2v B FirmwareOperating system
Affected:< 1.68
Wrc 2533gst2 FirmwareOperating system
Affected:< 1.31
Wrc X3200gst3 B FirmwareOperating system
Affected:< 1.27

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 ELECOM device model
    Log into the router web management interface and locate the device information or status page to confirm the exact model number (such as Wrc 1167gs2 B, Wrc X3200gst3 B, etc.)
    Affected if The device is an ELECOM wireless LAN router or repeater model not listed in the affected products section
  2. Locate the firmware version
    In the router web interface, navigate to the System, Status, or Firmware Information section to find the currently installed firmware version number
    Affected if The firmware version cannot be retrieved or is not displayed
  3. Compare firmware version against affected ranges
    Match your device model to the corresponding threshold: Wrc 1167gs2 B/Wrc 1167gs2h B requires >= 1.73, Wrc 1167gst2 requires >= 1.34, Wrc 2533gs2 B/W/Wrc 2533gs2v B requires >= 1.68, Wrc 2533gst2 requires >= 1.31, Wrc X3200gst3 B requires >= 1.27
    Affected if Your installed firmware version is lower than the required threshold for your specific model
  4. Verify web interface accessibility
    Confirm the router administrative web interface is reachable on the local network (typically at http://192.168.0.1 or http://elecom.setup)
    Affected if The admin interface is accessible and the firmware version is below the patched threshold - the CSRF vulnerability is then present

If you own an affected ELECOM router/repeater model and your firmware version is below the patched threshold (1.73 for 1167gs2, 1.34 for 1167gst2, 1.68 for 2533gs2 variants, 1.31 for 2533gst2, or 1.27 for X3200gst3), your device is vulnerable to CSRF attacks allowing unauthorized admin session hijacking.

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.

dbcve · scoped
Upgrade available Upgrade to 1.27 / 1.31 / 1.34 or later
Fixed in 1.271.311.34
Interim mitigation

Contact ELECOM for available firmware updates that address this CSRF vulnerability; implement anti-CSRF tokens, SameSite cookie attributes, and Origin/Referer header validation as compensatory measures until official patch is available.

Recommended fix Moderate confidence

Firmware 1.73 (Wrc 1167gs2 B/gs2h B), 1.34 (Wrc 1167gst2), 1.68 (Wrc 2533gs2 B/W/v B), 1.31 (Wrc 2533gst2), 1.27 (Wrc X3200gst3 B) or later

  1. 1. Identify the specific ELECOM device model from the affected product list (Wrc 1167gs2 B, Wrc 1167gs2h B, Wrc 1167gst2, Wrc 2533gs2 B, Wrc 2533gs2 W, Wrc 2533gs2v B, Wrc 2533gst2, or Wrc X3200gst3 B)
  2. 2. Access the device administration web interface or ELECOM support website (www.elecom.co.jp)
  3. 3. Navigate to the firmware update section for the specific device model
  4. 4. Download and install the latest firmware version: 1.73 or higher for Wrc 1167gs2 B/Wrc 1167gs2h B, 1.34 or higher for Wrc 1167gst2, 1.68 or higher for Wrc 2533gs2 B/W/Wrc 2533gs2v B, 1.31 or higher for Wrc 2533gst2, 1.27 or higher for Wrc X3200gst3 B
  5. 5. Verify the firmware update was successful by checking the web interface or device status
Caveat Review ELECOM release notes for any configuration changes required after firmware update; backup device configuration before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wrc 1167gs2 B Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23910 — 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-2024-23910 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