# CVE-2025-30237: Authentication Bypass via Broken Access Control in Web Server in Multiple TP-Link Aginet Devices

> Unauthenticated attackers can bypass authentication on TP-Link Aginet devices to execute privileged operations and gain full control.

- **Severity:** High 8.7 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-gcr6-hgjr-2h8p

## What is CVE-2025-30237?

CVE-2025-30237 is a high-severity authentication bypass vulnerability in TP-Link Systems Inc. EX141(BR) V1.0/1.9, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The affected TP-Link Aginet devices contain a flaw in the web management interface where authentication
checks are not consistently enforced on certain endpoints. An attacker can send
specially crafted requests to bypass authentication and directly invoke
privileged functionality without valid credentials. This issue arises from
improper enforcement of access control mechanisms on sensitive operations.

Successful
exploitation may allow an unauthenticated attacker to execute privileged
operations and gain full control of the device.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-30237?


## How do I fix CVE-2025-30237?

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

## Is CVE-2025-30237 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-30237 and fix it if it is affected.

What it is: CVE-2025-30237 is a high-severity authentication bypass vulnerability in TP-Link Systems Inc. EX141(BR) V1.0/1.9, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-30237 in the wild and no public exploit code.

Affected product: TP-Link Systems Inc. EX141(BR) V1.0/1.9. 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-2025-30237/ (Markdown: https://insights.sbomify.com/CVE-2025-30237/index.md)
```

## Sources

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

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