CVE-2023-37562
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 · uneditedCross-site request forgery (CSRF) vulnerability in exists in WTC-C1167GC-B v1.17 and earlier, and WTC-C1167GC-W v1.17 and earlier. If a user views a malicious page while logged in, unintended operations may be performed.
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 confidenceCross-site request forgery (CSRF) vulnerability in WTC-C1167GC-B and WTC-C1167GC-W wireless terminal controllers versions 1.17 and earlier allows attackers to induce authenticated users to perform unintended actions by tricking them into visiting malicious web pages.
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.17<= 1.17CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelLocate the wireless terminal controller on your network and confirm it is either Elecom WTC-C1167GC-B or WTC-C1167GC-W by checking the device label, web interface, or administrative consoleAffected if The device is not one of these two models
-
Access the firmware version informationLog into the device web administration panel or administrative interface and navigate to the system status, device information, or firmware version sectionAffected if Unable to retrieve firmware version information
-
Compare the installed firmware versionNote the displayed firmware version number and compare it against the affected range: version 1.17 or earlierAffected if Firmware version is 1.17 or lower (e.g., 1.17, 1.16, 1.15, etc.)
If the device is an Elecom WTC-C1167GC-B or WTC-C1167GC-W with firmware version 1.17 or earlier, the environment is affected by this CSRF vulnerability.
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.
dbcve · scopedUpgrade firmware to a version beyond v1.17 that includes CSRF protection, or implement anti-CSRF tokens for all state-changing operations and validate Origin/Referer headers.
Firmware version 1.18 or later (the first version after the affected v1.17 and earlier)
- Identify the current firmware version of the WTC-C1167GC-B or WTC-C1167GC-W device
- Access the device administration interface or use the official ELECOM configuration utility
- Navigate to the firmware update section
- Download the latest firmware version from the official ELECOM support page (www.elecom.co.jp)
- Follow the manufacturer's firmware upgrade instructions precisely
- Ensure the upgrade process is not interrupted by power loss or network disruption
- After upgrading, verify the new firmware version is installed
- Log out and log back in to confirm normal operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37562 — 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-37562 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