dbcve.org
Wrc F1167acf FirmwareOperating system · Elecom

CVE-2023-40069

CRITICAL · 9.8 CVSS v3.1 Published 2023-08-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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 an attacker who can access the product to execute an arbitrary OS command by sending a specially crafted request. Affected products and versions are as follows: WRC-F1167ACF all versions, WRC-1750GHBK all versions, WRC-1167GHBK2 all versions, WRC-1750GHBK2-I all versions, and WRC-1750GHBK-E all versions.

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

OS command injection vulnerability in ELECOM wireless LAN routers allows authenticated attackers who can access the device management interface to execute arbitrary OS commands by sending specially crafted requests. The vulnerability affects five WRC-series router models across all versions, indicating a systemic input validation flaw in the router firmware's web management interface.

MitigationSince all versions are affected with no explicit patch available, organizations should immediately restrict network access to the router management interface, consider replacing end-of-life devices, and monitor ELECOM for firmware updates. If continued use is required, implement network segmentation and strong authentication to reduce attack surface.

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 F1167acf FirmwareOperating system
Affected:all versions
Wrc 1750ghbk FirmwareOperating system
Affected:all versions
Wrc 1167ghbk2 FirmwareOperating system
Affected:all versions
Wrc 1750ghbk2 I FirmwareOperating system
Affected:all versions
Wrc 1750ghbk E FirmwareOperating system
Affected:all versions

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 the router model
    Access the router's web management interface (typically at 192.168.0.1 or 192.168.1.1) and check the device status or firmware version page. Alternatively, check the device label or documentation.
    Affected if The device is one of: WRC-F1167ACF, WRC-1750GHBK, WRC-1167GHBK2, WRC-1750GHBK2-I, or WRC-1750GHBK-E
  2. Confirm firmware version
    In the router web interface, navigate to System or Status section to view the installed firmware version. Note that all versions are affected.
    Affected if Any firmware version is displayed (all versions are vulnerable)
  3. Determine management interface exposure
    Check if the router web management interface is accessible from the internet or an untrusted network segment. Use external port scanning tools (nmap -p 80,443 <external-ip>) or review firewall rules.
    Affected if The management interface (HTTP/HTTPS on port 80/443 or custom ports) is reachable from untrusted networks
  4. Verify authentication status
    Attempt to access the router login page. Check if default credentials are still in use (common ELECOM defaults include admin/admin, admin/password, or no password). Review stored credential configurations.
    Affected if The interface uses default, weak, or no authentication credentials, or is accessible without additional network barriers

The environment is affected if an ELECOM WRC-series router model (F1167acf, 1750ghbk, 1167ghbk2, 1750ghbk2-I, or 1750ghbk-E) has its management interface exposed to untrusted networks or uses weak authentication.

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

Since all versions are affected with no explicit patch available, organizations should immediately restrict network access to the router management interface, consider replacing end-of-life devices, and monitor ELECOM for firmware updates. If continued use is required, implement network segmentation and strong authentication to reduce attack surface.

Fix this in Wrc F1167acf Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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