CVE-2025-65128
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe ZBT WE2001 router firmware 23.09.27 has a missing authentication check in its web management API. Certain API endpoints with function names ending in '*_nocommit' can be invoked without any authentication, allowing any local network attacker to modify critical router settings including Wi-Fi SSIDs, wireless credentials, and administrative passwords by supplying the expected parameters.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the router modelLog into the router web interface or check the device label to confirm the model is ZBT WE2001Affected if The device is NOT a ZBT WE2001 router - different models are not affected by this CVE
-
Check the installed firmware versionAccess the router web management interface and navigate to the Status or System Information page to find the firmware version. Alternatively, check the file named 'firmware.bin' if you have access to the device filesystem or backup.Affected if The firmware version is 23.09.27 or falls within an unpatched version range; patched versions are NOT affected
-
Verify the web management API is accessibleAttempt to reach the router web interface HTTP/HTTPS ports from your local network using a browser or curl command (e.g., curl http://<router-ip>/). Check if the login page or API responds.Affected if The web management interface is accessible from the network - this is required for the vulnerability to be exploitable
-
Test for unauthenticated *_nocommit endpoint accessFrom a local network host, send a crafted HTTP request to a known *_nocommit endpoint (e.g., http://<router-ip>//cgi-bin/luci/api/<function>_nocommit) with parameters for Wi-Fi or admin settings, observing if the request succeeds without authentication.Affected if The *_nocommit endpoint responds successfully or modifies settings without requiring authentication - this confirms the vulnerability is present
You are affected if you have a ZBT WE2001 router running firmware 23.09.27 (or an unpatched version) AND the web management API is accessible from your local network, allowing unauthenticated access to *_nocommit endpoints.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor firmware patches when available; until then, restrict local network access to trusted devices only and consider network segmentation to limit exposure.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-65128 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-65128 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data