dbcve.org
X6000r FirmwareOperating system · Totolink

CVE-2026-4611

HIGH · 8.8 CVSS v3.1 Published 2026-03-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 flaw has been found in TOTOLINK X6000R 9.4.0cu.1360_B20241207/9.4.0cu.1498_B20250826. Affected by this issue is the function setLanCfg of the file /usr/sbin/shttpd. Executing a manipulation of the argument Hostname can lead to os command injection. The attack may be launched remotely.

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 TOTOLINK X6000R router firmware (versions 9.4.0cu.1360 and 9.4.0cu.1498) contains an OS command injection vulnerability in the setLanCfg function within the shttpd web server daemon (/usr/sbin/shttpd). The Hostname parameter passed to this function is not properly sanitized before being used in OS command execution, allowing remote attackers to inject and execute arbitrary OS commands by manipulating the Hostname argument.

MitigationApply vendor firmware patches when available; until then, restrict administrative web interface access to trusted networks only, disable remote management interfaces exposed to the internet, and consider network segmentation to limit exposure.

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
X6000r FirmwareOperating system
Affected:= 9.4.0cu.1360_b20241207= 9.4.0cu.1498_b20250826

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 firmware version
    Access the router web interface (typically at 192.168.0.1 or 192.168.1.1), navigate to System or Status settings, and locate the firmware version information. Alternatively, use the command 'grep -i version /proc/mtd' or check the bootloader output if you have console access.
    Affected if The firmware version matches 9.4.0cu.1360_B20241207 or 9.4.0cu.1498_B20250826 exactly.
  2. Confirm the web server is accessible
    Attempt to reach the router's web interface via HTTP or HTTPS on the default LAN IP address. Verify that /usr/sbin/shttpd is running by checking process list if you have shell access via telnet/SSH.
    Affected if The web interface responds and the shttpd process is running, exposing the vulnerable function.
  3. Verify LAN configuration interface is available
    Log into the router web interface and navigate to LAN settings or Network > LAN configuration page. Look for Hostname or LAN IP settings that can be modified.
    Affected if The LAN configuration page with Hostname field is accessible and accepts user input.
  4. Check for command injection indicators
    Review router logs or system logs for unusual commands or shell executions. If you have telnet/SSH access, check /var/log/messages or the output of 'ps' for unexpected shell processes spawned from the httpd parent process.
    Affected if Logs show execution of unexpected commands or shell metacharacters in process listings related to the httpd service.

The device is affected if it runs TOTOLINK X6000R firmware version 9.4.0cu.1360_B20241207 or 9.4.0cu.1498_B20250826 and has its web interface accessible with LAN configuration settings exposed.

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 patches when available; until then, restrict administrative web interface access to trusted networks only, disable remote management interfaces exposed to the internet, and consider network segmentation to limit exposure.

Fix this in X6000r Firmware 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-2026-4611 — 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-2026-4611 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