Skip to main content

TOTOLINK X6000R EUVDEUVD-2026-92908

| CVE-2026-105484 CRITICAL
OS Command Injection (CWE-78)
2026-10-06 VulDB GHSA-34j5-jp28-25g9
10.0
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach device web interface (AV:N)
  2. Delivery
    Send crafted request to /cgi-bin/cstecgi.cgi
  3. Exploit
    Inject shell metacharacters into file_name
  4. Execution
    Trigger command injection in firmware_check
  5. Persist
    Execute arbitrary OS commands as root
  6. Impact
    Full device compromise

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization OS command sanitization, avoid shell exec
MITRE ATT&CK

2 techniques across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation targets the UploadFirmwareFile handler's firmware_check routine reached via the /cgi-bin/cstecgi.cgi endpoint on TOTOLINK X6000R firmware 9.4.0cu.652_B20230116; the attacker must be able to reach this web management interface over the network and supply a malicious file_name argument containing shell metacharacters. Per the CVSS vector (PR:N/UI:N) no authentication or user interaction is required, though firmware-upload handlers on such routers are sometimes reachable only after login - if that holds here, exploitation is limited to authenticated or LAN-adjacent attackers. Real-world exposure is further limited to devices whose management interface is reachable from the attacker's position (e.g. WAN-exposed admin interface, or an attacker already on the LAN), and to the specific affected firmware build.

Impact

All severity signals point to maximum theoretical risk: the vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes remote, low-complexity, unauthenticated exploitation with full high impact to confidentiality, integrity and availability on both the vulnerable and subsequent systems (score 10.0), consistent with CWE-78 OS command injection yielding device takeover. However, the supporting exploitation-likelihood signals are either absent or weak: no EPSS score is provided, the CVE is not listed in CISA KEV, and no POC flag is set in the input, so there is no public exploit identified at time of analysis. The E:X (Exploit Maturity: Not Defined) in the vector confirms exploitation status is undetermined rather than proven. This is sourced from a single reporter (VulDB) with no corroborating independent or vendor advisory. Net assessment: a genuinely critical-by-design flaw that warrants prompt patching on exposed devices, but the lack of KEV/EPSS/POC evidence means there is no confirmation of real-world mass exploitation yet - treat as high-priority-to-remediate, not as a confirmed active threat. Note also the firmware-upload handler context: such endpoints sometimes require prior authentication in practice, which would contradict the PR:N rating - verify the actual auth requirement with the vendor.

Exploit ScenarioDerived

A remote attacker sends a crafted HTTP request to /cgi-bin/cstecgi.cgi targeting the UploadFirmwareFile handler's firmware_check function, embedding shell metacharacters in the file_name argument. Because the value is passed into an OS command without sanitization, the injected commands execute on the router with the web service's privileges (typically root on these devices). No public exploit was identified at time of analysis, though the attack is straightforward given low complexity and no required privileges per the CVSS vector.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 2.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 06, 2026

OS command injection in the TOTOLINK X6000R wireless router (firmware 9.4.0cu.652_B20230116) allows remote attackers to execute arbitrary shell commands on the device by supplying a crafted file_name argument that is processed by the firmware_check routine behind the /cgi-bin/cstecgi.cgi endpoint. The vendor-derived CVSS 4.0 vector scores this 10.0 (AV:N/AC:L/AT:N/PR:N/UI:N, with high confidentiality, integrity and availability impact on both the vulnerable and subsequent systems), and our independent assessment is consistent: CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H, indicating low-complexity, unauthenticated remote exploitation with scope change and full device compromise. No public exploit code or confirmed active exploitation (CISA KEV) was identified at the time of analysis, and real-world exposure is limited to units whose web management interface is reachable from the attacker's position - a WAN-exposed admin interface or an attacker already positioned on the LAN.

RemediationAI

No vendor-released patch was identified at the time of analysis, so remediation must currently rely on exposure reduction and compensating controls rather than a fixed firmware version. The highest-value control is to remove the attack surface: disable WAN-side access to the router's web management interface (disable remote management / port-forwarded admin access, and block inbound TCP to the admin HTTP/HTTPS ports at the perimeter firewall), which prevents the unauthenticated remote path described by the CVSS vectors but does not protect against an attacker already on the LAN. Restrict administrative access to a trusted management VLAN or a small allow-list of source addresses, and change default administrative credentials - trade-off: this adds management friction and still leaves authenticated abuse possible if the handler only requires a session. Where the firmware-upload functionality is not needed, avoid exposing or using the /cgi-bin/cstecgi.cgi UploadFirmwareFile path, and monitor router logs and outbound traffic for unexpected shell activity or connections from the device; note that logging on consumer routers is limited, so detection value is partial. Check https://vuldb.com/vuln/413619 and https://www.totolink.net/ for an updated firmware release and apply it as soon as the vendor publishes one, since only a firmware update can remove the underlying command-injection flaw.

Affected VersionsENISA

X6000R 9.4.0cu.652_B20230116

Affected Packages

euvd x6000r no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability is a classic OS command injection (CWE-78) rooted in the failure to neutralize shell metacharacters before passing user-controlled input to a system command. In this case the affected element is the firmware_check function reachable through the UploadFirmwareFile handler in /cgi-bin/cstecgi.cgi, a CGI back-end typical of TOTOLINK/Realtek-based consumer routers; the file_name argument is incorporated into a shell invocation without sanitization, so metacharacters such as semicolons, backticks or command substitution are interpreted by the underlying shell running with the web service's privileges. Because the handler is part of the firmware-upload workflow, it executes in a highly privileged context on the router. The affected product is identified by CPE cpe:2.3:a:totolink:x6000r:*:*:*:*:*:*:*:*, where the wildcard version means the vendor's CPE does not constrain an exact build, but exploitation has been demonstrated against firmware 9.4.0cu.652_B20230116. Both the CVSS 4.0 vector (PR:N/UI:N) and the independent CVSS 3.1 vector (PR:N/UI:N) describe the injection as unauthenticated and requiring no user interaction; however, firmware-upload handlers on this class of device are sometimes gated behind an authenticated session, so if that gate applies to the firmware_check path, exploitation would in practice be limited to authenticated or LAN-adjacent attackers - the assessment explicitly flags this as an open caveat rather than a confirmed restriction.

Know when X6000R gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 10.0 CRITICAL
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
vuln.today AI 10.0 CRITICAL

Remote, low-complexity, unauthenticated command injection per vector; OS command execution escapes the CGI component to the router OS, so S:C with full C/I/A impact.

3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
High
Subsequent system: Integrity
High
Subsequent system: Availability
High

DescriptionCVE.org

A security vulnerability has been detected in TOTOLINK X6000R 9.4.0cu.652_B20230116. The impacted element is the function firmware_check of the file /cgi-bin/cstecgi.cgi of the component UploadFirmwareFile Handler. Such manipulation of the argument file_name leads to os command injection. The attack may be performed from remote.

Executive ViewAI

Why It Matters

TOTOLINK X6000R wireless routers on firmware 9.4.0cu.652_B20230116 can be fully taken over by an unauthenticated remote attacker, who gains the ability to run arbitrary commands on the device and reach the networks it connects. With no vendor patch available, every affected unit is a standing exposure point for the sites, branches, or remote locations where it is deployed. Leadership should care because a compromised edge router can be used to intercept or alter traffic, disable connectivity, and serve as a foothold into the wider corporate network.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: disable or firewall off WAN-side access to the web management interface, restrict administration to a dedicated management VLAN or trusted host allowlist, block inbound requests to /cgi-bin/cstecgi.cgi at the network perimeter, segment affected routers away from sensitive systems, monitor for anomalous outbound traffic or unexpected command execution, and plan replacement of the affected units.

Threat Intelligence Overview

EPSS Score
2.1%
Top 19% exploitable
Prevalence
Low
consumer/SOHO router brand, limited and regional global footprint
Social Media
3
Sightings
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 2.1%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Total

Priority Score

52
Low Medium High Critical
KEV: 0
EPSS: +2
CVSS: +50
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

OS command injection occurs when an application passes unsanitized user input directly into system shell commands.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy