CVE-2026-1601VulnerabilityPublished 29 Jan 2026Updated 23 Feb 2026

CVE-2026-1601: Totolink A7000R · Command Injection

Affects Totolink A7000RSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 2.1% chance of exploitation in 30 days – higher than 82% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
TotolinkA7000R	Affected =4.1cu.4154	Fixed in–

AI-suggested

1. Immediately isolate affected Totolink A7000R devices from untrusted networks to limit exposure to remote attacks. 2. Disable remote management interfaces or restrict access to trusted IP addresses only. 3. Monitor network traffic for unusual activity indicative of exploitation attempts targeting /cgi-bin/cstecgi.cgi endpoints. 4. Implement network segmentation to contain potential breaches originating from compromised routers. 5. 6. Employ intrusion detection/prevention systems (IDS/IPS) with signatures targeting known exploit patterns for this vulnerability. 7. Consider replacing vulnerable devices with models from vendors with stronger security track records if patching is not feasible. 8. Educate network administrators on the risks of command injection and the importance of secure configuration and timely updates. 9. Use network access control (NAC) to enforce device compliance and prevent vulnerable devices from connecting to critical network segments. 10. Conduct penetration testing and vulnerability assessments to identify and remediate similar weaknesses in network infrastructure.

Description

A weakness has been identified in Totolink A7000R 4.1cu.4154. The impacted element is the function setUploadUserData of the file /cgi-bin/cstecgi.cgi. Executing a manipulation of the argument FileName can lead to command injection. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks.

Impact

The vulnerability allows remote attackers to execute arbitrary commands on affected Totolink A7000R routers, potentially leading to full device compromise. This can result in unauthorized access to internal networks, interception or manipulation of network traffic, disruption of network services, and use of compromised devices as pivot points for further attacks. Organizations relying on these routers for critical network connectivity could face confidentiality breaches, integrity violations, and availability outages. The exploitability without authentication and user interaction increases the risk of automated attacks and worm-like propagation within vulnerable networks. The public availability of exploit code further elevates the threat landscape, potentially enabling widespread exploitation once attackers incorporate it into their toolkits. The absence of patches prolongs exposure, especially in environments where firmware updates are infrequent or poorly managed. The impact is particularly severe for enterprises, ISPs, and critical infrastructure operators using this router model, as compromise could undermine network security and operational continuity.

Summary

CVE-2026-1601 identifies a command injection vulnerability in the Totolink A7000R router firmware version 4.1cu.4154. The vulnerability resides in the setUploadUserData function of the /cgi-bin/cstecgi.cgi endpoint. Specifically, the FileName parameter is improperly sanitized, allowing an attacker to inject arbitrary shell commands. This flaw can be exploited remotely without requiring authentication or user interaction, leveraging the network accessibility of the device's management interface. The vulnerability's CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P) indicates network attack vector, low attack complexity, no authentication, and partial impact on confidentiality, integrity, and availability. Although the impact on confidentiality, integrity, and availability is limited, successful exploitation could allow attackers to execute arbitrary commands with elevated privileges, potentially leading to full device compromise, unauthorized network access, or disruption of services. The exploit code has been publicly released, increasing the risk of exploitation despite no current reports of active attacks. No official patches or mitigations have been released by Totolink at this time, leaving affected devices vulnerable. The vulnerability highlights the risks of insufficient input validation in embedded device web interfaces, emphasizing the need for secure coding practices and timely firmware updates.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 21:47 UTC

Technical details

References

Community reviews

Related threats