# CVE-2026-42961: Cross-site request forgery in WAB-BE187-M

> Attackers can trick logged-in users into performing unintended operations on ELECOM wireless access points due to inadequate CSRF token handling.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 May 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-9q5w-fvxj-wgpq

## What is CVE-2026-42961?

CVE-2026-42961 is a medium-severity vulnerability in ELECOM CO.,LTD. WAB-BE187-M, published on 13 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

ELECOM wireless LAN access point devices implement CSRF protection mechanism, but with inadequate handling of CSRF tokens. If a user views a malicious page while logged in, the user may be tricked to do unintended operations.

Weakness: CWE-344 (Use of Invariant Value in Dynamically Changing Context)

## Which versions are affected by CVE-2026-42961?


## How do I fix CVE-2026-42961?

No fix has been published for CVE-2026-42961 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-42961 being exploited?

There is no known exploitation of CVE-2026-42961 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-42961 and fix it if it is affected.

What it is: CVE-2026-42961 is a medium-severity vulnerability in ELECOM CO.,LTD. WAB-BE187-M, published on 13 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-42961 in the wild and no public exploit code.

Affected product: ELECOM CO.,LTD. WAB-BE187-M. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-42961/ (Markdown: https://insights.sbomify.com/CVE-2026-42961/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-42961
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-42961
- OSV: https://osv.dev/vulnerability/CVE-2026-42961

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-42961/
Summaries are generated and may contain mistakes; the official description above is the record.