Summary
CVE-2026-51711 is an incorrect access control vulnerability (CWE-284) in the setWiFiWpsStart function of the TOTOLINK T6 router web management interface, firmware version 4.1.5cu.748_B20211015. The flaw allows an unauthenticated remote attacker to send a crafted POST request to /cgi-bin/cstecgi.cgi and open a Wi-Fi Protected Setup (WPS) pairing window without any credentials. The issue carries a CVSS v3.1 base score of 9.1 (Critical) and requires no user interaction to exploit.
Technical details
- Root cause: the
setWiFiWpsStarthandler incstecgi.cgidoes not verify that the requesting client is authenticated before acting on the request. - Trigger condition: sending an HTTP POST request to
/cgi-bin/cstecgi.cgicontaining{"topicurl":"setWiFiWpsStart"}along with WPS mode parameters. - Attack vector: network-based, no authentication or user interaction required (AV:N/AC:L/PR:N/UI:N).
- Impact: an attacker can remotely activate WPS pairing mode on the device, opening a window during which unauthorized wireless clients may be able to join the network — undermining the confidentiality and integrity of the wireless network without needing valid credentials.
Affected software
- TOTOLINK T6, firmware version 4.1.5cu.748_B20211015
Severity
- CVSS v3.1 Base Score: 9.1 (Critical)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Mitigation and recommended actions
- Immediate: No official patched firmware version has been identified as of this writing; check TOTOLINK’s support/download page for the T6 model regularly for an updated firmware release that addresses this issue.
- If no patch is available: Restrict access to the router’s web management interface (
/cgi-bin/cstecgi.cgi) to trusted internal networks only, and disable remote/WAN-side administration. - Disable WPS functionality on the device if it is not required, to eliminate the exposed attack surface.
- Monitor devices joining the wireless network for unauthorized or unexpected clients, particularly around unexplained WPS pairing events.
- Consider replacing or isolating affected devices on a segmented network if they cannot be updated.
How IONIX identifies potentially affected assets
IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.
- Raw response body:
/cgi-bin/cstecgi.cgi,N600R (Firmware version V...),TOTOLINK

