dbcve.org
X5000r FirmwareOperating system · Totolink

CVE-2025-13184

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-10
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
Public exploit 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
Unauthenticated Telnet enablement via cstecgi.cgi (auth bypass) leading to unauthenticated root login with a blank password on factory/reset X5000R V9.1.0u.6369_B20230113 (arbitrary command execution). Earlier versions that share the same implementation, may also be affected.

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 X5000R router firmware V9.1.0u.6369_B20230113 contains an authentication bypass vulnerability in the cstecgi.cgi web interface. An unauthenticated attacker can enable the Telnet service remotely via this endpoint, and on factory/reset state the device allows root login with a blank password. This combination provides unauthenticated remote command execution with root privileges.

MitigationUpdate to a patched firmware version when released by the vendor. In the interim, disable remote Telnet access, ensure the device is not in factory/reset state with default credentials, and restrict network access to the management interface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
X5000r FirmwareOperating system
Affected:= 9.1.0u.6369_b20230113

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Check the installed firmware version
    Access the router web interface (typically http://192.168.1.1) and navigate to the status or system info page to view the firmware version. Alternatively, check via telnet or SSH if already enabled.
    Affected if The firmware version shown is exactly 9.1.0u.6369_b20230113
  2. Verify the cstecgi.cgi endpoint is accessible
    Attempt to access the web endpoint at /cstecgi.cgi on the router's IP address using a web browser or curl command.
    Affected if The endpoint responds (even with an error) indicating the web interface is accessible
  3. Confirm Telnet service is not enabled
    Scan the router's IP address for open port 23 (Telnet) using nmap or by running 'telnet <router-ip>' to test connectivity.
    Affected if Port 23 is open and responds, indicating Telnet service is running
  4. Check if device is in factory reset state
    Attempt to log into the Telnet service (if enabled) with username 'root' and blank password, or check the router configuration for credential settings.
    Affected if Login succeeds with root/blank password, indicating the device retains factory default credentials
  5. Determine if web management interface is exposed remotely
    Check router firewall settings to see if the web interface (port 80/443) is accessible from WAN/external networks, or attempt to access the router's IP from outside the local network.
    Affected if Remote management is enabled and the web interface is reachable from outside the local network

You are affected if your device runs firmware version 9.1.0u.6369_b20230113, the cstecgi.cgi endpoint is accessible, and either Telnet is enabled or the device remains in factory reset state with default credentials.

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

Update to a patched firmware version when released by the vendor. In the interim, disable remote Telnet access, ensure the device is not in factory/reset state with default credentials, and restrict network access to the management interface.

Fix this in X5000r Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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