dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2024-25568

HIGH · 8.8 CVSS v3.1 Published 2024-04-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click

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
OS command injection vulnerability in ELECOM wireless LAN routers allows a network-adjacent unauthenticated attacker to execute arbitrary OS commands by sending a specially crafted request to the product. Affected products and versions are as follows: WRC-X3200GST3-B v1.25 and earlier, WRC-G01-W v1.24 and earlier, and WMC-X1800GST-B v1.41 and earlier. Note that WMC-X1800GST-B is 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 · high confidence

OS command injection vulnerability in ELECOM wireless LAN routers allows a network-adjacent unauthenticated attacker to execute arbitrary OS commands by sending specially crafted requests. The vulnerability affects three router models and their firmware versions up to the specified limits.

MitigationApply vendor-supplied firmware updates (WRC-X3200GST3-B v1.26+, WRC-G01-W v1.25+, WMC-X1800GST-B v1.42+) to patch the command injection flaw. Until patched, restrict access to the router's management interface to trusted users on trusted networks.

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

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/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 router model
    Check the product label on the router or log into the web management interface to view the device model information
    Affected if Model is WRC-X3200GST3-B, WRC-G01-W, or WMC-X1800GST-B
  2. Check firmware version
    Access the router admin panel (typically via web browser at 192.168.x.x) and navigate to System or Firmware settings to view the current firmware version
    Affected if Firmware version cannot be determined or is below vendor fixed versions
  3. Compare against fixed versions
    Compare your installed firmware version to the known patched versions: WRC-X3200GST3-B (1.26+), WRC-G01-W (1.25+), WMC-X1800GST-B (1.42+)
    Affected if Installed version is lower than the fixed version for your model (e.g., below 1.26 for WRC-X3200GST3-B)
  4. Verify management interface exposure
    Check if the router web management interface is accessible from external networks or untrusted segments
    Affected if Management interface is exposed to untrusted networks (this is the attack vector for exploitation)

Your router is affected if it is one of the three ELECOM models and runs firmware version lower than the patched release for that model.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware updates (WRC-X3200GST3-B v1.26+, WRC-G01-W v1.25+, WMC-X1800GST-B v1.42+) to patch the command injection flaw. Until patched, restrict access to the router's management interface to trusted users on trusted networks.

Recommended fix Moderate confidence

Firmware version higher than the vulnerable release (v1.26+ for WRC-X3200GST3-B, v1.25+ for WRC-G01-W, v1.42+ for WMC-X1800GST-B) - verify latest version on ELECOM support page

  1. 1. Identify the exact model of your ELECOM wireless LAN router (WRC-X3200GST3-B, WRC-G01-W, or WMC-X1800GST-B)
  2. 2. Check the current firmware version installed on the device through the router's web administration interface
  3. 3. Visit the official ELECOM support page at www.elecom.co.jp to download the latest firmware for your specific model
  4. 4. If a newer firmware version is available (higher than v1.25 for WRC-X3200GST3-B, v1.24 for WRC-G01-W, or v1.41 for WMC-X1800GST-B), download it
  5. 5. Follow the firmware update instructions provided in the ELECOM manual to apply the update
  6. 6. After updating, verify the firmware version has been successfully upgraded
  7. 7. As a general security practice, change default credentials and disable any unnecessary remote management features
Caveat Firmware updates typically do not introduce breaking changes for normal operation, but always backup configuration before updating

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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