dbcve.org
Wab S300iw Pd FirmwareOperating system · Elecom

CVE-2026-24465

CRITICAL · 9.8 CVSS v3.0 Published 2026-02-03
Fix available
A fix is available. Upgrade to 1.13 / 5.5.02 or later.
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
Stack-based buffer overflow vulnerability exists in ELECOM wireless LAN access point devices. A crafted packet may lead to arbitrary code execution.

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

A stack-based buffer overflow vulnerability in ELECOM wireless LAN access points allows remote attackers to execute arbitrary code via specially crafted packets. The critical severity (CVSS 9.8) indicates the flaw is network-exploitable without authentication, likely in the packet processing path of the wireless interface or management service.

MitigationApply vendor-provided firmware updates to all affected ELECOM wireless access point devices immediately. If no patch is available, consider network segmentation to limit exposure and disable unnecessary management interfaces.

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
Wab S300iw Pd FirmwareOperating system
Affected:all versions
Wab S733iw Pd FirmwareOperating system
Affected:all versions
Wrc X1500gsa B FirmwareOperating system
Affected:< 1.13
Wrc X1500gs B FirmwareOperating system
Affected:< 1.13
Wab S300iw2 Pd FirmwareOperating system
Affected:< 5.5.02
Wab S300iw Ac FirmwareOperating system
Affected:< 5.5.02
Wab S733iw2 Pd FirmwareOperating system
Affected:< 5.5.02
Wab S733iw Ac FirmwareOperating system
Affected:< 5.5.02

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.0/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 exact ELECOM access point model
    Check the device label, administrative web interface (usually at 192.168.1.1 or 192.168.0.1), or the status page in the firmware for the exact model number (e.g., WRC-X1500GS-B, WAB-S300iw, etc.)
    Affected if The model matches any of the affected products listed in the CVE (Wab S300iw Pd, Wab S733iw Pd, Wrc X1500gsa B, Wrc X1500gs B, Wab S300iw2 Pd, Wab S300iw Ac, Wab S733iw2 Pd, Wab S733iw Ac)
  2. Determine the installed firmware version
    Log into the device administrative interface and navigate to System Status, Firmware Information, or similar section to view the current firmware version; alternatively, check via CLI if SSH/Telnet is enabled
    Affected if The firmware version is lower than the patched version (1.13 for Wrc X1500gsa B/Wrc X1500gs B, 5.5.02 for Wab S300iw2/Wab S733iw2/Wab S300iw Ac/Wab S733iw Ac, or any version for Wab S300iw Pd/Wab S733iw Pd which are affected in all versions)
  3. Verify the wireless radio is enabled
    In the web administrative interface, check the Wireless Settings or Radio Settings section to confirm the wireless access point functionality is turned on
    Affected if The wireless interface is enabled and the device is acting as an access point (the vulnerability is triggered via specially crafted wireless packets)
  4. Assess network exposure of the management interface
    Check the device IP configuration and determine if the administrative interface (HTTP/HTTPS) is accessible from untrusted networks (WAN/Internet) rather than only from isolated LAN segments
    Affected if The device management interface is exposed to untrusted networks or the wireless radio is accessible to untrusted users without additional filtering

You are affected if your device model matches one of the affected ELECOM products AND your firmware version falls within the vulnerable ranges (or is an all-versions model) AND the wireless functionality is enabled, as the stack overflow is triggered during packet processing.

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.

dbcve · scoped
Upgrade available Upgrade to 1.13 / 5.5.02 or later
Fixed in 1.135.5.02
Interim mitigation

Apply vendor-provided firmware updates to all affected ELECOM wireless access point devices immediately. If no patch is available, consider network segmentation to limit exposure and disable unnecessary management interfaces.

Recommended fix Moderate confidence

Wrc X1500gsa B/Wrc X1500gs B: upgrade to firmware >= 1.13; Wab S300iw2 Pd/Wab S300iw Ac/Wab S733iw2 Pd/Wab S733iw Ac: upgrade to firmware >= 5.5.02; Wab S300iw Pd/Wab S733iw Pd: contact vendor

  1. 1. Identify the exact model number and current firmware version of your ELECOM wireless access point device
  2. 2. For Wrc X1500gsa B and Wrc X1500gs B: Download firmware version 1.13 or later from www.elecom.co.jp
  3. 3. For Wab S300iw2 Pd, Wab S300iw Ac, Wab S733iw2 Pd, Wab S733iw Ac: Download firmware version 5.5.02 or later from www.elecom.co.jp
  4. 4. Access the device web management interface or use the ELECOM firmware update utility
  5. 5. Upload the new firmware file and initiate the update process
  6. 6. Wait for the update to complete and verify the device reboots successfully
  7. 7. Confirm the new firmware version is installed and the device is operational
  8. 8. For Wab S300iw Pd and Wab S733iw Pd (all versions affected): Contact ELECOM support directly to inquire about available firmware updates or remediation options
Caveat Standard firmware update - ensure stable power during upgrade process to avoid bricked device

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

Fix this in Wab S300iw Pd Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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