CA300-POE · CVE-2026-124058 · Infrastructure
NO FIX YET
A buffer overflow in setWiFiRepeaterConfig (argument ApCliKeyStr, /cgi-bin/cstecgi.cgi) of TOTOLINK CA300-PoE 6.2c.884. VulDB says it can be attacked remotely but needs an authenticated session. A public proof of concept exists. The sources do not say what an attacker can run after the overflow, and no fixed firmware is known.
first public Nov 7, 2026 · 2 sources
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
TOTOLINK CA300-PoE devices running firmware 6.2c.884 are affected. VulDB says exploitation needs an authenticated session on the web management interface, so this is not a pre-login flaw, but a public proof of concept exists. Risk is highest where the admin interface is reachable from the internet or shared networks, or the admin password is default or weak. Devices with management access limited to a trusted network can treat this as lower priority. No fixed firmware has been found.
Not affected if management-interface-not-exposed, other-firmware
Who cares auth-required, ca300-poe, embedded, iot, router, totolink
Unknown from the sources.
A weakness has been identified in TOTOLINK CA300-PoE 6.2c.884. Affected is the function setWiFiRepeaterConfig of the file /cgi-bin/cstecgi.cgi. Executing a manipulation of the argument ApCliKeyStr can lead to buffer overflow. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.