On this page (6 sections)
A command injection flaw, tracked as CVE-2026-121931, has been published for the Linksys WRT54GL running version 4.30.18. According to the NVD record, it sits in the traceroute diagnostic function of the router's web interface and can be triggered remotely.
The record states that the exploit has been disclosed publicly, that the vendor did not respond when contacted, and that the product is no longer supported. If you run one of these routers at an office, a shop or a client site, you should plan to isolate or replace it.
What happened
The NVD entry, published on 2026-11-04, describes a flaw in the function system of the file apply.cgi, part of the Traceroute Diagnostic Function. Manipulating the argument traceroute_ip leads to OS command injection. The same entry says the attack can be launched remotely and that the exploit has been disclosed publicly and may be used.
The entry also says the vendor was contacted early about the disclosure and did not respond in any way. It adds that the vulnerability only affects products that are no longer supported by the maintainer. The references include a public write-up on GitHub and VulDB entries. So far only one independent publisher covers this story, so details beyond the CVE record are limited.
What the weakness means in plain terms
Router diagnostic pages such as traceroute take a host name or IP address from the user and hand it to a system command. Command injection happens when the firmware does not strictly validate that input, so extra text is interpreted by the operating system as part of the command. The result is that someone who can reach the feature may be able to run commands on the router itself.
A router sits between your network and the internet, so control of it can mean traffic interception, DNS changes, or use of the device in attacks on others. The research does not say whether authentication is required to reach the vulnerable function, so assume it may be exposed to anyone who can reach the admin interface.
Who is affected
The record names only Linksys WRT54GL version 4.30.18. It does not list other versions or other Linksys models, so do not assume that other devices are or are not affected based on this record alone.
Realistic exposure depends on who can reach the router's web interface. Devices with remote administration enabled on the internet are at the greatest risk. Devices that can only be managed from the internal network are less exposed, but still at risk if a device on that network is compromised.
How to check your exposure
First confirm the model and firmware version. Look at the label on the device and the status or firmware page in the admin interface. Then check whether the admin page is reachable from outside your network.
This command, run from a machine outside your network (for example a mobile hotspot), shows whether something answers on the web port of your public IP address. Replace the placeholder with your own address. A connection that is refused or times out is the result you want:
curl -I --max-time 10 http://YOUR_PUBLIC_IP/Also review the router's settings for any remote management option and note whether it is on. The label and location vary by firmware, so check the admin pages directly.
What to do now
No vendor patch is known, and the record says the product is unsupported. The practical answer is to reduce exposure now and replace the device.
- Identify every WRT54GL in use, including at client and branch sites
- Disable remote (internet-facing) administration
- Restrict admin access to a single trusted wired computer or management VLAN
- Change the admin password to a long, unique one
- Do not use the traceroute or other diagnostic tools until the device is replaced
- Check the router's DNS and DHCP settings for changes you did not make
- Plan a replacement with a supported router that still receives security updates
- Keep a record of the replacement date so the old device is actually retired
Detection and monitoring
Because exploitation is unconfirmed, watch for general signs of router compromise: unexpected DNS server addresses, new port forwards, unexplained reboots, and unusual outbound traffic. If your router logs can be sent to another system, keep them there.
For the websites behind the router, monitor from outside. Webforta Monitor can alert on uptime, certificate and DNS changes, which can help you notice if traffic is being redirected. This does not detect the router flaw itself. You can also run the free SSL checker after any network incident to confirm your certificates are still the ones you expect.
If you suspect a device was taken over, follow the steps in website hacked: what to do and change credentials used across that network.
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.
