CVE-2023-37566
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 · uneditedCommand injection vulnerability in ELECOM and LOGITEC wireless LAN routers allows a network-adjacent authenticated attacker to execute an arbitrary command by sending a specially crafted request to the web management page. Affected products and versions are as follows: WRC-1167GHBK3-A v1.24 and earlier, WRC-1167FEBK-A v1.18 and earlier, WRC-F1167ACF2 all versions, WRC-600GHBK-A all versions, WRC-733FEBK2-A all versions, WRC-1467GHBK-A all versions, WRC-1900GHBK-A all versions, and LAN-W301NR 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 · high confidenceCommand injection vulnerability in the web management interface of ELECOM and LOGITEC wireless LAN routers allows an authenticated attacker with network adjacency to execute arbitrary OS commands by injecting them into web request parameters. The vulnerability affects eight router models, with several having no fixed versions available (all versions affected).
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<= 1.24<= 1.18CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify router modelLocate the device label on the router or access the web management interface to view the model name. Confirm it matches one of the affected ELECOM or LOGITEC models including Wrc 1167ghbk3 A or Wrc 1167febk A.Affected if The router is an ELECOM or LOGITEC model listed as affected by this CVE.
-
Check firmware versionLog into the web management interface and navigate to the firmware or status page to view the installed firmware version. Compare against the affected version ranges provided.Affected if Firmware version is at or below 1.24 for Wrc 1167ghbk3 A, at or below 1.18 for Wrc 1167febk A, or any version for other affected models with no fixed versions.
-
Verify web management exposureCheck router firewall settings and network configuration to determine if the web management interface (HTTP/HTTPS on ports 80/443 or similar) is accessible from the WAN or untrusted networks rather than only from the LAN.Affected if The web management interface is exposed to WAN or untrusted networks, increasing the attack surface.
-
Assess authentication statusReview user accounts configured on the router and determine whether default credentials are still in use or if strong, unique passwords have been set for administrative access.Affected if Default credentials remain unchanged or weak authentication is configured, allowing authenticated attacker access required for exploitation.
-
Check for indicators of compromiseReview router logs for suspicious commands, unexpected configuration changes, or unknown administrative accounts. Monitor network traffic for unusual outbound connections from the router.Affected if Logs or network activity show evidence of unauthorized command execution or unexpected configuration modifications.
The environment is affected if the router is one of the vulnerable ELECOM or LOGITEC models with a firmware version within the affected range or with no available patch, combined with web interface exposure and accessible authentication.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor-supplied firmware updates when available; for end-of-life devices without patches, consider network segmentation to limit exposure and monitor for indicators of compromise, as the authentication requirement reduces but does not eliminate exploitation risk.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37566 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-37566 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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