dbcve.org
Wrc 1167gst2 FirmwareOperating system · Elecom

CVE-2022-25915

HIGH · 8.8 CVSS v3.1 Published 2022-03-31
Fix available
A fix is available. Upgrade to after 2.11 or later.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click Patch available

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
Improper access control vulnerability in ELECOM LAN routers (WRC-1167GST2 firmware v1.25 and prior, WRC-1167GST2A firmware v1.25 and prior, WRC-1167GST2H firmware v1.25 and prior, WRC-2533GS2-B firmware v1.52 and prior, WRC-2533GS2-W firmware v1.52 and prior, WRC-1750GS firmware v1.03 and prior, WRC-1750GSV firmware v2.11 and prior, WRC-1900GST firmware v1.03 and prior, WRC-2533GST firmware v1.03 and prior, WRC-2533GSTA firmware v1.03 and prior, WRC-2533GST2 firmware v1.25 and prior, WRC-2533GST2SP firmware v1.25 and prior, WRC-2533GST2-G firmware v1.25 and prior, and EDWRC-2533GST2 firmware v1.25 and prior) allows a network-adjacent authenticated attacker to bypass access restriction and to access the management screen of the product via unspecified vectors.

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

A detailed technical summary for this CVE is being prepared.

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 1167gst2 FirmwareOperating system
Affected:<= 1.25
Wrc 1167gst2a FirmwareOperating system
Affected:<= 1.25
Wrc 1167gst2h FirmwareOperating system
Affected:<= 1.25
Wrc 2533gs2 B FirmwareOperating system
Affected:<= 1.52
Wrc 2533gs2 W FirmwareOperating system
Affected:<= 1.52
Wrc 1750gs FirmwareOperating system
Affected:<= 1.03
Wrc 1750gsv FirmwareOperating system
Affected:<= 2.11
Wrc 1900gst FirmwareOperating system
Affected:<= 1.03

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

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
Upgrade available Upgrade to a release after 2.11
Vendor patch www.elecom.co.jp →
Recommended fix Moderate confidence

Firmware version newer than the vulnerable thresholds (e.g., v1.26 or later for most WRC-1167GST2 models, v1.53 or later for WRC-2533GS2 models)

  1. 1. Identify the specific ELECOM router model from the affected product list (WRC-1167GST2, WRC-1167GST2A, WRC-1167GST2H, WRC-2533GS2-B, WRC-2533GS2-W, WRC-1750GS, WRC-1750GSV, or WRC-1900GST)
  2. 2. Access the router's web management interface using credentials
  3. 3. Navigate to the firmware update or system settings section
  4. 4. Download the latest firmware from ELECOM's official support page: https://www.elecom.co.jp/products/
  5. 5. Upload and apply the firmware update to remediate the improper access control vulnerability
  6. 6. After updating, verify that firmware version is newer than the vulnerable versions (e.g., v1.26+ for WRC-1167GST2 series, v1.53+ for WRC-2533GS2 series)
Caveat Review ELECOM release notes for any configuration changes required after firmware update

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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