CVE-2023-37565
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 · uneditedCode injection vulnerability in ELECOM wireless LAN routers allows a network-adjacent authenticated attacker to execute arbitrary code by sending a specially crafted request. Affected products and versions are as follows: WRC-1167GHBK-S v1.03 and earlier, WRC-1167GEBK-S v1.03 and earlier, WRC-1167FEBK-S v1.04 and earlier, WRC-1167GHBK3-A v1.24 and earlier, and WRC-1167FEBK-A v1.18 and earlier.
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 confidenceCode injection vulnerability in ELECOM WRC-1167 series wireless LAN routers allows a network-adjacent authenticated attacker to execute arbitrary code by sending specially crafted requests to the router's management interface.
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.03<= 1.03<= 1.04<= 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 modelLog into the router web management interface and check the status or device info page for the exact model name (WRC-1167GHBK-S, WRC-1167GEBK-S, WRC-1167FEBK-S, WRC-1167GHBK3-A, or WRC-1167FEBK-A)Affected if Model is not one of the five affected WRC-1167 series variants listed in the CVE
-
Check installed firmware versionIn the router admin interface, navigate to the firmware or system status page and note the exact firmware version number displayedAffected if Firmware version falls within any of these ranges: WRC-1167GHBK-S <= 1.03, WRC-1167GEBK-S <= 1.03, WRC-1167FEBK-S <= 1.04, WRC-1167GHBK3-A <= 1.24, WRC-1167FEBK-A <= 1.18
-
Verify management interface accessibilityConfirm the router management web interface (HTTP/HTTPS on ports 80 or 443, or custom port) is reachable from the networkAffected if The management interface is exposed to an untrusted network (not just localhost or a trusted management VLAN)
-
Confirm authentication stateCheck whether the router requires authentication for management interface access, and review if default credentials are in useAffected if The management interface is accessible without authentication or using factory-default credentials
A user is affected if they have a WRC-1167 series router model listed in the CVE running a firmware version at or below the specified threshold, with the management interface accessible from the network.
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 dataUpdate router firmware to versions newer than those affected (v1.04+ for WRC-1167FEBK-S, v1.25+ for WRC-1167GHBK3-A, v1.19+ for WRC-1167FEBK-A, v1.04+ for WRC-1167GHBK-S and WRC-1167GEBK-S). If patching is not immediately possible, restrict network access to trusted users only.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37565 — 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-37565 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