/

CVE-2026-51709

Severity:

CRITICAL RISK

(9.8)

Broken Access Control (CWE-284) in TOTOLINK T6 Wi-Fi

CVE-2026-51709

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Unauthorized Wi-Fi configuration changes and network disruption

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A critical access-control vulnerability in the TOTOLINK T6 allows unauthenticated attackers to change primary Wi-Fi settings through a crafted POST request.

The issue becomes risky when the device exposes the affected management endpoint and does not require authentication before applying configuration changes.

Affected context

The vulnerability occurs in the setWiFiBasicCfg function of TOTOLINK T6 firmware 4.1.5cu.748_B20211015. Deployments may be exposed when the device's CGI management interface is reachable and the affected endpoint accepts configuration requests without verifying the caller's identity or permissions.

Exploit preconditions

  • Attack surface: The device's HTTP CGI management interface
  • Required access: No authentication is required when the affected behavior is exposed
  • Trigger point: A POST request to /cgi-bin/cstecgi.cgi that reaches setWiFiBasicCfg
  • Why exploitation is possible: The function applies primary Wi-Fi configuration changes without enforcing appropriate access controls

Why this happens

The underlying bug is an authorization failure in a configuration-changing administrative function. The endpoint treats a client request as sufficiently trusted without first establishing an authenticated identity and verifying permission to modify wireless settings. This behavior maps to CWE-284: Improper Access Control, where protected functionality is accessible without the controls intended to restrict it.

Potential impact

  • An attacker may change the wireless network name or security settings
  • Legitimate users could lose access to the network
  • Network traffic may be redirected to an attacker-controlled wireless configuration
  • The device could be subjected to persistent configuration tampering
  • Downstream systems may be exposed to increased unauthorized access risk

General mitigation guidance

Mitigation generally focuses on ensuring that every configuration-changing endpoint is protected by authentication and authorization checks before processing input.

Common defensive patterns include:

  • Requiring authenticated, authorized sessions for administrative operations
  • Applying server-side authorization checks independently of client-supplied fields
  • Restricting management interfaces to trusted administrative networks
  • Using secure-by-default wireless settings and preserving them when validation fails
  • Separating read-only status operations from privileged configuration operations
  • Applying least privilege to management services and limiting administrative exposure
  • Invalidating or rotating administrative sessions and credentials after suspected tampering

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis and code review rules requiring authorization checks before configuration writes
  • Tests that invoke administrative endpoints without credentials and verify that changes are rejected
  • Review of CGI routing and dispatch logic for unauthenticated access to state-changing functions
  • Monitoring for unexpected POST requests to management endpoints and unexplained Wi-Fi configuration changes
  • Policy enforcement requiring management interfaces to be isolated from untrusted networks
  • Automated security review tools that identify state-changing endpoints lacking authentication or authorization controls

Sources

SourceLink
github.comgithub.com/DarkBoulder/CVE-Vendor-Coordination/blob/main/TOTOLINK/README.md
github.comgithub.com/ShengWu00/CVE-Vendor-Coordination/blob/main/TOTOLINK/README.md
totolink.nettotolink.net/
totolink.nettotolink.net/home/menu/detail/menu_listtpl/download/id/190/ids/36.html

Frequently asked

questions

It may be remotely exploitable when the device's management interface is reachable by an attacker. Exploitability depends on network exposure and deployment controls.

No authenticated account is required when the affected endpoint is accessible and the described unauthenticated behavior is present.

Require authentication and explicit authorization before any Wi-Fi configuration change is accepted, and reject unauthorized requests before processing or applying their contents.

Treat all configuration-changing endpoints as privileged operations, test them with unauthenticated and low-privilege clients, restrict management-plane exposure, and monitor for unexpected configuration changes.

Find out what's already
exploitable in your codebase.