dbcve.org
X5000r FirmwareOperating system · Totolink

CVE-2025-70327

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-23
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
TOTOLINK X5000R v9.1.0cu_2415_B20250515 contains an argument injection vulnerability in the setDiagnosisCfg handler of the /usr/sbin/lighttpd executable. The ip parameter is retrieved via websGetVar and passed to a ping command through CsteSystem without validating if the input starts with a hyphen (-). This allows remote authenticated attackers to inject arbitrary command-line options into the ping utility, potentially leading to a Denial of Service (DoS) by causing excessive resource consumption or prolonged execution.

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

TOTOLINK X5000R v9.1.0cu_2415_B20250515 has an argument injection in the setDiagnosisCfg handler of lighttpd. The ip parameter passed to the ping command is not validated to reject input starting with a hyphen, allowing an authenticated attacker to inject ping options like -w (wait seconds) or -c (count) to cause DoS through extended ping execution.

MitigationImplement input validation to reject the ip parameter if it begins with a hyphen character, or use option termination (e.g., -- separator) when invoking ping to prevent option injection.

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.0cu.2415_b20250515

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. Identify router model
    Access the router web interface or check device label to confirm the model is TOTOLINK X5000R
    Affected if The device is not a TOTOLINK X5000R router, the vulnerability does not apply
  2. Check firmware version
    Access router web interface (typically at 192.168.1.1) and navigate to System > Firmware Upgrade or Status page to view the installed firmware version
    Affected if Firmware version is not 9.1.0cu.2415_b20250515, the specific affected version is not present
  3. Verify lighttpd web server is running
    Check if the lighttpd web server process is running on the device, typically accessible on port 80 or 443
    Affected if The lighttpd web server is not running, the attack surface does not exist
  4. Confirm diagnostic feature is accessible
    Log into the router web interface and locate the diagnostic or ping functionality (setDiagnosisCfg handler), typically under Network or Maintenance sections
    Affected if The diagnostic feature is not accessible or requires authentication to access, the injection point cannot be reached
  5. Inspect the ip parameter handling
    If you have access to the router filesystem, examine the binary or script handling the setDiagnosisCfg request and verify if the ip parameter is passed directly to the ping command without hyphen validation
    Affected if The ip parameter is validated to reject values starting with a hyphen, the vulnerability may already be patched

You are affected if you have a TOTOLINK X5000R router running firmware version 9.1.0cu.2415_b20250515 with the diagnostic feature accessible via the lighttpd web server and no validation on the ip parameter.

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

Implement input validation to reject the ip parameter if it begins with a hyphen character, or use option termination (e.g., -- separator) when invoking ping to prevent option injection.

Fix this in X5000r Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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