On this page (7 sections)
CVE-2026-123960 is a buffer overflow in the TOTOLINK CA300-PoE, firmware 6.2c.884. It sits in the setWanConfig function of the web management script /cgi-bin/cstecgi.cgi and can be reached remotely. According to the GitHub Advisory Database entry, an exploit has been made public and could be used for attacks.
If you run this device, manage it for clients, or have it on a network that hosts a website or office systems, you should limit access to its admin interface now. The advisory lists no patched version at the time of writing.
What happened
On November 7, 2026, the vulnerability was published through the National Vulnerability Database and mirrored to the GitHub Advisory Database. The description says a manipulation of the pppoeUser, priDns or secDns argument in setWanConfig can lead to a buffer overflow, that the attack can be launched remotely, and that the exploit is public.
Coverage is thin. Only one independent publisher has covered this so far, and the NVD record repeats the same description, so it is not separate confirmation. The GitHub entry is marked unreviewed and lists affected and patched versions as unknown. Treat the details as credible but not yet independently verified.
Technical details
A buffer overflow happens when a program copies input into a fixed-size memory area without checking its length. Extra data spills into adjacent memory, which can crash the process or, in worse cases, change how the program behaves. The weakness is tracked as CWE-119 and CWE-120.
Here the input is three parameters handled by the WAN configuration function: pppoeUser (a PPPoE username) and priDns and secDns (primary and secondary DNS server values). The affected code is in the device's CGI handler, the program behind its web admin interface.
The CVSS v4 metrics in the advisory describe a network attack vector, low attack complexity, no attack requirements, low privileges required and no user interaction. Impact on confidentiality, integrity and availability is rated high for both the vulnerable and subsequent systems. The advisory does not describe what an attacker actually achieves in practice, so do not assume more than those ratings.
Who is affected
The only version named is 6.2c.884 of the TOTOLINK CA300-PoE. The advisory lists affected versions as unknown, so other firmware builds may or may not be vulnerable. Until TOTOLINK says otherwise, treat any CA300-PoE as potentially exposed.
Realistic exposure depends on who can reach the management interface:
- Devices with the web admin page reachable from the internet carry the highest risk.
- Devices on flat office or home networks where any compromised laptop or guest device can reach the admin page.
- Agencies and managed service providers that deployed these units for clients and may not have them in an inventory.
How to check your exposure
First, find out whether you have this device and which firmware it runs. The version usually appears in the device's admin interface on a status or system page.
Next, check whether the admin interface is reachable from outside. From a machine that is not on your local network, such as a phone on mobile data, try opening the device's public address in a browser. If a login page loads, the interface is exposed. You can also review the port-forwarding and remote management settings on your upstream router or firewall.
If you keep access logs from a front-end proxy or firewall, this read-only search lists requests to the vulnerable script path. Run it on a Linux host that holds the logs, replacing the path with your log file:
grep "/cgi-bin/cstecgi.cgi" /path/to/access.logRequests from addresses you do not recognize, especially with unusually long values, deserve a closer look. Normal admin use will also match, so this is a lead for investigation and not proof of compromise.
What to do now
The advisory lists no patch, so the focus is reducing who can reach the device. Check the TOTOLINK website for firmware updates and install one if its notes say it addresses this CVE.
- Inventory every TOTOLINK CA300-PoE you run and note its firmware version.
- Disable remote (internet-facing) administration and remove any port forwards to the admin interface.
- Restrict the admin interface to a trusted management network or specific admin IP addresses.
- Change the device's admin password to a long, unique one, since the CVSS vector lists only low privileges as required.
- Check TOTOLINK's site and support channels for a fixed firmware release, and apply it after reading its notes.
- Review the device's configuration for changes you did not make, especially WAN and DNS settings.
- If the device cannot be restricted and no fix appears, consider replacing it or placing it behind a firewall that blocks access to its management page.
Detection and monitoring
A successful memory-corruption attack on an embedded device may leave few traces, so combine several signals:
- Watch for unexpected reboots or crashes of the device, which can occur when an overflow fails.
- Alert on changes to WAN, PPPoE and DNS settings.
- Monitor outbound DNS queries from your network for resolvers you do not use.
- Log and review access to the management interface from outside your admin network.
Watching from the outside also helps if a website sits behind this network. Webforta Monitor tracks uptime, certificate and DNS changes, and the free SSL checker lets you confirm your certificate has not changed unexpectedly. Neither inspects or fixes the device itself.
If you suspect the device was compromised, follow our guide on what to do when a website is hacked, and rotate credentials that passed through the network.
What we do not know yet
- Whether TOTOLINK has released a fix or acknowledged the report; none is listed in the advisory.
- Which other firmware versions are affected.
- Whether attacks in the wild have occurred. The advisory says only that the exploit is public and could be used, and the record shows no CISA Known Exploited Vulnerabilities listing.
- The precise outcome of a successful attack, since the advisory describes the overflow and CVSS ratings but not practical impact.
We will update this article if TOTOLINK or another primary source adds details.
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.
