# CVE-2025-65128: Missing authorization in n/a

> Unauthenticated attackers on the local network can modify router configurations, including Wi-Fi credentials and admin passwords, via the web management API.

- **Severity:** High 8.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A: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:** 11 Feb 2026
- **Updated:** 17 Feb 2026
- **Also known as:** GHSA-v66c-4xgf-59c7

## What is CVE-2025-65128?

CVE-2025-65128 is a high-severity missing authorization vulnerability in n/a, published on 11 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A missing authentication mechanism in the web management API components of Shenzhen Zhibotong Electronics ZBT WE2001 23.09.27 allows unauthenticated attackers on the local network to modify router and network configurations. By invoking operations whose names end with "*_nocommit" and supplying the parameters expected by the invoked function, an attacker can change configuration data, including SSID, Wi-Fi credentials, and administrative passwords, without authentication or an existing session.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2025-65128 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65128 is a high-severity missing authorization vulnerability in n/a, published on 11 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65128 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-2025-65128/ (Markdown: https://insights.sbomify.com/CVE-2025-65128/index.md)
```

## Sources

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

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