dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-64075

CRITICAL · 10.0 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 →
100/100
Remediation priority · Urgent
Remotely reachable 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 path traversal vulnerability in the check_token function of Shenzhen Zhibotong Electronics ZBT WE2001 23.09.27 allows remote attackers to bypass authentication and perform administrative actions by supplying a crafted session cookie value.

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 · moderate confidence

A path traversal vulnerability in the check_token function of ZBT WE2001 firmware 23.09.27 allows remote attackers to bypass authentication by providing a specially crafted session cookie value. The vulnerability enables unauthenticated attackers to perform administrative actions on the device.

MitigationApply available firmware patches from Zhibotong Electronics; if no patch exists, implement network segmentation to limit exposure and consider compensating controls such as web application firewall rules to detect path traversal patterns in cookie values.

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

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
    Access the device web interface or check the device label/marketing materials to confirm it is a ZBT WE2001 router. Look for Zhibotong Electronics branding or the WE2001 model designation.
    Affected if The device is not a ZBT WE2001 model, the vulnerability does not apply.
  2. Determine the installed firmware version
    Log into the router web interface and navigate to the System or Status page to view the firmware version. Alternatively, check the firmware file name if you have admin access to the device via SSH or Telnet.
    Affected if The firmware version is 23.09.27 or earlier unpatched versions. If the firmware version is unknown or cannot be verified, assume potential exposure.
  3. Verify web management interface accessibility
    Attempt to access the router web interface from a browser using the device IP address (typically 192.168.1.1 or similar). Confirm the login page loads and accepts cookie-based sessions.
    Affected if The web management interface is exposed to untrusted networks (such as the internet), increasing the likelihood of remote exploitation.
  4. Inspect session cookie behavior
    Using browser developer tools or a proxy tool, capture a session cookie after authentication. Examine whether the cookie value contains any path-like patterns or encoded traversal sequences that could be manipulated.
    Affected if The device uses session cookies that are validated through the check_token function without proper sanitization, making authentication bypass possible.
  5. Test for authentication bypass
    Using a tool like curl or Burp Suite, send an HTTP request to the router with a crafted cookie value containing path traversal sequences (e.g., ../../) and observe if administrative actions are permitted without valid credentials.
    Affected if Administrative actions succeed with manipulated cookie values, confirming the vulnerability is present and exploitable.

You are affected if you have a ZBT WE2001 device running firmware version 23.09.27 or earlier with its web interface accessible, and administrative actions can be performed using a specially crafted session cookie value containing path traversal sequences.

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 available firmware patches from Zhibotong Electronics; if no patch exists, implement network segmentation to limit exposure and consider compensating controls such as web application firewall rules to detect path traversal patterns in cookie values.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64075 — 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-64075 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