dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2025-65127

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
A lack of session validation in the web API component of Shenzhen Zhibotong Electronics ZBT WE2001 23.09.27 allows remote unauthenticated attackers to access administrative information-retrieval functions intended for authenticated users. By invoking "get_*" operations, attackers can obtain device configuration data, including plaintext credentials, 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 confidence

The ZBT WE2001 router firmware (version 23.09.27) has a session validation bypass in its web API component. Unauthenticated remote attackers can invoke 'get_*' API operations to retrieve sensitive device configuration data, including plaintext credentials, without any valid session token or authentication.

MitigationApply vendor firmware patch when available; until then, restrict network access to the device's administrative interface using firewall rules or network segmentation to prevent unauthenticated API access.

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
None
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Check the router label or access the administrative web interface to confirm the model is ZBT WE2001
    Affected if The device is not a ZBT WE2001 router, then it is not affected by this specific CVE
  2. Check the firmware version
    Access the router admin panel (typically http://192.168.1.1 or similar) and navigate to System Status or Firmware Upgrade page to view the installed firmware version; alternatively, check the startup logs or firmware file metadata
    Affected if The firmware version is 23.09.27 - only this specific version is listed as affected
  3. Verify the web API is accessible
    Attempt to access the device's web API endpoint - typically http://<device_ip>/cgi-bin/luci or similar API paths; check if HTTP/HTTPS ports (80/443 or custom) are open and responding
    Affected if The web interface is not accessible from your network segment, reducing exposure but not changing the vulnerable version status
  4. Test for unauthenticated API access
    Send a crafted GET request to a 'get_*' API endpoint (such as http://<device_ip>/cgi-bin/luci/api/<something> or similar path that returns device configuration) without including any session token, cookie, or authentication header
    Affected if The API returns sensitive configuration data or credentials without requiring authentication - this confirms the vulnerability is present and exploitable
  5. Check network exposure
    Review firewall rules and network segmentation to determine if the router admin interface is exposed to untrusted networks or the internet
    Affected if The administrative interface is directly accessible from untrusted networks, the vulnerability can be exploited by remote attackers

You are affected only if you have a ZBT WE2001 router running firmware version 23.09.27 with its web API interface accessible to untrusted networks, and the 'get_*' API endpoints respond without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware patch when available; until then, restrict network access to the device's administrative interface using firewall rules or network segmentation to prevent unauthenticated API access.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-65127 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-65127 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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