Quick answers
- Is CVE-2026-42948 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-42948 being exploited in the wild.
- How severe is CVE-2026-42948?
- Medium severity, with a CVSS score of 4.8, published 13 May 2026.
- Which products and versions are affected?
- Elecom WAB-BE187-M v1.1.10 and earlier; Elecom WAB-BE36-M v1.1.3 and earlier; Elecom WAB-BE36-S v1.1.3 and earlier; Elecom WAB-BE72-M v1.1.3 and earlier.
- Is there a fix for CVE-2026-42948?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-42948 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-42948?
- Check whether you run Elecom WAB-BE187-M, Elecom WAB-BE36-M, Elecom WAB-BE36-S or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A stored cross-site scripting (XSS) vulnerability exists in the web management interface of several ELECOM wireless LAN access points. The flaw stems from inadequate sanitization of the 'hostname' parameter. An attacker with administrative privileges can inject malicious JavaScript into this field, which is then stored on the device. When another administrator accesses the management page where this data is displayed, the script executes within the context of their session. This can lead to unauthorized actions being performed on behalf of the victim administrator. Users are advised to update to the latest firmware versions provided by the vendor.
Affected products
- ELECOM WAB-BE187-M v1.1.10 and earlier
- ELECOM WAB-BE72-M v1.1.3 and earlier
- ELECOM WAB-BE36-M v1.1.3 and earlier
- ELECOM WAB-BE36-S v1.1.3 and earlier
Timeline
- 2026-05-12: advisory: Initial advisory published by JVN/JPCERT
- 2026-05-13: disclosed: CVE record published