CVE-2026-5975
OS Command Injection in Totolink A7100RU CGI Handler (setDmzCfg
Publication date: 2026-04-09
Last updated on: 2026-04-09
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| totolink | a7100ru | 7.4cu.2313_b20191024 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-77 | The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. |
| CWE-78 | The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-5975 is a remote command injection vulnerability found in the TOTOLINK A7100RU router, version 7.4cu.2313_b20191024. It exists in the CGI Handler component, specifically in the function setDmzCfg within the file /cgi-bin/cstecgi.cgi.
The vulnerability arises because the function processes a user-supplied parameter named "wanIdx" improperly. This parameter is inserted into a buffer and then executed as an operating system command without proper sanitization, allowing an attacker to inject arbitrary OS commands.
An attacker can exploit this by sending crafted HTTP POST requests to the router, causing it to execute malicious commands remotely.
How can this vulnerability impact me? :
This vulnerability allows remote attackers to execute arbitrary operating system commands on the affected router without any authentication.
- Attackers can take full control of the router, potentially altering its configuration or using it as a foothold to attack other devices on the network.
- It can lead to data interception, network disruption, or the installation of malicious software.
- Because the exploit is publicly available, the risk of exploitation is high.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for suspicious HTTP POST requests to the endpoint /cgi-bin/cstecgi.cgi that include a crafted payload manipulating the "wanIdx" parameter.
A practical detection method is to capture and analyze network traffic for POST requests containing JSON data with the "wanIdx" parameter set to suspicious command injection patterns, such as backticks or command execution syntax.
- Use a network packet capture tool like tcpdump or Wireshark to filter HTTP POST requests to /cgi-bin/cstecgi.cgi.
- Example tcpdump command to capture relevant traffic: tcpdump -i <interface> -A 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)' | grep '/cgi-bin/cstecgi.cgi'
- Inspect captured HTTP POST payloads for the presence of "wanIdx" parameters containing suspicious command injection patterns, such as backticks (`) or shell commands.
- Alternatively, use web application firewall (WAF) or intrusion detection system (IDS) rules to detect and alert on POST requests with "wanIdx" parameters containing command injection patterns.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the vulnerable endpoint and applying input validation or filtering to prevent command injection.
Specifically:
- Limit remote access to the router's management interface, especially blocking access to /cgi-bin/cstecgi.cgi from untrusted networks.
- If possible, disable or restrict the CGI Handler component that processes the "wanIdx" parameter.
- Monitor and block suspicious HTTP POST requests targeting /cgi-bin/cstecgi.cgi with unusual "wanIdx" values.
- Apply any available firmware updates or patches from the vendor that address this vulnerability.
Since the exploit is publicly available and can be triggered remotely without authentication, prompt action is critical to prevent compromise.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify how CVE-2026-5975 affects compliance with common standards and regulations such as GDPR or HIPAA.