Loading vulnerability…
OS Command Injection in Totolink A7100RU setWiFiBasicCfg
CVE-2026-5977 affects Totolink A7100RU firmware version 7.4cu.2313_b20191024. The vulnerability is an OS command injection flaw in the CGI Handler component, specifically in the setWiFiBasicCfg function exposed through /cgi-bin/cstecgi.cgi. According to the provided content, improper handling of the wifiOff argument allows attacker-controlled input to reach an operating system command context, resulting in command injection. The issue is remotely exploitable over the network, and public exploit information is available.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can allow a remote attacker to execute arbitrary operating system commands on the affected device without privileges or user interaction. Based on the provided CVSS vectors and description, this can result in full compromise of the router's confidentiality, integrity, and availability, including unauthorized configuration changes, disruption of network services, and potential use of the device as a foothold for further activity on the local network.
If you can’t patch tonight, do this now.
If no patched firmware is available, restrict access to the affected CGI interface /cgi-bin/cstecgi.cgi to trusted management networks only, disable remote administration from untrusted networks, and place the device behind firewall rules that prevent external access to the web management interface. Monitor for suspicious requests targeting setWiFiBasicCfg or manipulating the wifiOff parameter, and consider replacing the device if vendor support or fixes are not available.
Patch, then assume compromise.
Upgrade Totolink A7100RU firmware to a vendor-fixed version if one is available. The vulnerable code path in setWiFiBasicCfg should be corrected so that the wifiOff parameter is not incorporated into shell commands in an unsafe manner. Proper remediation would include eliminating shell invocation where possible, using parameterized or fixed-function APIs instead of command construction, and implementing strict server-side input validation and allowlisting for the affected parameter.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.