Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-105484 – Unauthenticated OS Command Injection (RCE) – TOTOLINK X6000R 9.4.0cu.652_B20230116

Be the first to know when new zero-days emerge:

Summary

CVE-2026-105484 is a critical, unauthenticated OS command injection vulnerability in the firmware upload handler of the TOTOLINK X6000R wireless router. The flaw resides in the firmware_check function of the UploadFirmwareFile handler, reachable via /cgi-bin/cstecgi.cgi, and allows a remote attacker to execute arbitrary operating system commands on the device without any authentication. The issue is rated CRITICAL with a maximum CVSS v3.1 base score of 10.0.

Technical details

  • Root cause: The firmware_check function fails to properly sanitize the file_name parameter before using it in a system-level operation, enabling OS command injection (CWE-78 / CWE-77).
  • Trigger conditions: An attacker submits a crafted file_name value to the firmware upload endpoint (UploadFirmwareFile handler) on /cgi-bin/cstecgi.cgi.
  • Attack vector: Network-based and does not require authentication or any user interaction, making it exploitable by any remote attacker who can reach the device’s management interface.
  • Impact: Full compromise of confidentiality, integrity, and availability of the device — successful exploitation can lead to arbitrary command execution with the privileges of the web management process, potentially resulting in complete device takeover.

Affected software

  • TOTOLINK X6000R, firmware version 9.4.0cu.652_B20230116

Severity

  • CVSS v3.1 Base Score: 10.0 (CRITICAL)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: No vendor-supplied patched firmware version has been publicly confirmed as of this writing. Check the TOTOLINK official website for firmware updates for the X6000R and apply any available update immediately.
  • If no patch is available:
    • Restrict access to the device’s web management interface (/cgi-bin/cstecgi.cgi) so it is not reachable from the public internet.
    • Place management interfaces behind a VPN or firewall rule limiting access to trusted internal networks/IPs only.
    • Disable remote/WAN-side administration on the router if not strictly required.
    • Monitor for unexpected firmware upload requests or anomalous outbound connections from the device.
    • Consider replacing or isolating end-of-life TOTOLINK devices that do not receive security updates.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge