# CVE-2026-30702: Auth bypass in n/a

> Attackers can bypass authentication on the WiFi Extender WDR201A web interface by directly accessing restricted endpoints, gaining unauthorized access.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Mar 2026
- **Updated:** 23 Mar 2026
- **Also known as:** GHSA-4mf8-x363-f56c

## What is CVE-2026-30702?

CVE-2026-30702 is a critical authentication bypass vulnerability in n/a, published on 18 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WiFi Extender WDR201A (HW V2.1, FW LFMZX28040922V1.02) implements a broken authentication mechanism in its web management interface. The login page does not properly enforce session validation, allowing attackers to bypass authentication by directly accessing restricted web application endpoints through forced browsing

Weakness: CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2026-30702 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30702 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-30702 is a critical authentication bypass vulnerability in n/a, published on 18 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30702 exists.

Affected product: n/a. 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-30702/ (Markdown: https://insights.sbomify.com/CVE-2026-30702/index.md)
```

## Sources

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

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