On this page (6 sections)
A critical OS command injection flaw, tracked as CVE-2026-121932, has been published for the Linksys E5350 router running firmware 1.0.00.037. According to the NVD record, the attack may be initiated remotely, a public exploit exists, and the vendor did not respond when contacted about the disclosure.
If you run an E5350 at an office, a shop, or a client site, treat it as exposed until proven otherwise. No fixed firmware is mentioned in the research, so the practical goal is to limit who can reach the router's web interface.
What was disclosed
The NVD entry, published 2026-11-04, says the flaw affects the function system in the file /wizard/apply.cgi. Manipulating the arguments ping_ip or traceroute_ip leads to OS command injection. The record states the exploit is public and may be used, and that the vendor was contacted early but never replied.
The record lists a write-up in a public GitHub repository and several VulDB entries as references. The folder name in that repository suggests an unauthenticated (pre-auth) path, but the NVD text itself does not say whether login is required, so treat authentication requirements as unconfirmed.
Why command injection on a router is serious
Routers often expose diagnostic tools such as ping and traceroute in their web interface. These features pass a user-supplied address to an operating system command. If the device does not strictly validate that input, an attacker can append their own commands, which then run on the router itself, usually with high privileges.
A compromised router sits in front of every device on the network. Realistic consequences include traffic interception, DNS changes that redirect users, use of the device in botnets, and a foothold for reaching internal systems. For website owners, that can mean exposed admin sessions or tampered traffic between your office and your hosting. These are general risks of router compromise, not confirmed outcomes of this specific flaw.
Who is realistically exposed
- Small offices, shops and home offices using a Linksys E5350 on firmware 1.0.00.037.
- Agencies and developers who work from such a router and log in to client dashboards, hosting panels or SSH from behind it.
- Anyone whose router web interface is reachable from the internet, or from a guest or untrusted LAN segment.
- Other firmware versions or models are not mentioned in the research. Do not assume they are safe; check with the vendor or your own testing.
How to check your exposure
First confirm the model and firmware version. In the router's admin page, look under the status or firmware section for the model name and version number. If it reads E5350 with 1.0.00.037, you are in the affected group.
Next, check whether the admin interface is reachable from outside. From a device that is not on your network (for example a phone on mobile data), try opening your public IP address in a browser. You can find your public IP from the router's status page. If a login page loads, remote administration is likely enabled.
You can also review your own network from the inside. The following command lists hosts on your local subnet that have ports 80 or 443 open, if you have nmap installed. Run it only on networks you own or administer, and replace the address range with your own. Look for devices answering that you did not expect.
nmap -p 80,443 --open 192.168.1.0/24Any host answering on port 80 or 443 that you did not expect deserves a closer look. Check logs for repeated requests to /wizard/apply.cgi if your router or an upstream proxy keeps access logs, though most consumer routers do not.
What to do now
The research names no patch, so mitigation means reducing reach and watching for vendor news.
- Confirm whether your E5350 runs firmware 1.0.00.037.
- Disable remote (WAN) administration in the router settings.
- Restrict the admin interface to a single trusted wired device if the router allows it.
- Keep untrusted devices and guest Wi-Fi away from the management interface.
- Check the vendor's support page for a firmware update and install it if one appears.
- Change the admin password and Wi-Fi passwords if you suspect tampering.
- Review DNS settings on the router for entries you did not set.
- Plan a replacement with a supported model if the vendor stays silent.
Detection and monitoring
Signs of compromise on a router include unexplained configuration changes, a changed DNS server, unfamiliar port forwards, unexpected reboots, and unusual outbound traffic. Compare current settings against a saved backup if you have one.
For the websites behind the network, outside-in monitoring helps you spot knock-on effects such as unexpected certificate or DNS changes. Webforta Monitor tracks certificate, DNS and header changes, and the free SSL checker lets you verify what certificate your visitors actually see. These watch your sites, not the router itself, so they complement rather than replace router hardening.
If you suspect a breach, follow the steps in Website hacked: what to do and rotate credentials used from behind the affected router. For broader guidance on protecting a small business, see small business website security.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
