/

CVE-2026-51690

Severity:

CRITICAL RISK

(9.1)

Improper Access Control (CWE-284) in TOTOLINK T6 Router

CVE-2026-51690

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Unauthorized Configuration Modification

Severity:

CRITICAL RISK

(9.1)

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 router's setWanCfg function allows unauthenticated requests to modify upstream WAN provisioning and connectivity settings.

An attacker who can reach the router's CGI interface may send a specially crafted POST request to alter network behavior without first proving authorization.

Affected context

The vulnerability occurs in TOTOLINK T6 firmware version 4.1.5cu.748_B20211015 when the setWanCfg function processes requests through /cgi-bin/cstecgi.cgi without adequately enforcing authorization. Risk depends on the CGI interface being reachable by an attacker and on the device accepting WAN configuration changes through that endpoint.

Exploit preconditions

  • Attack surface: The router's HTTP CGI interface at /cgi-bin/cstecgi.cgi
  • Required access: Network reachability to the management or CGI service; valid authentication may not be required
  • Trigger point: Processing of a crafted POST request invoking the setWanCfg function
  • Why exploitation is possible: The function does not sufficiently verify authorization before applying upstream WAN configuration changes

Why this happens

The underlying flaw is an authorization-enforcement failure in a sensitive configuration handler. The setWanCfg function accepts requests that can modify WAN settings without consistently checking whether the caller has the required privileges.

This maps to CWE-284: Improper Access Control, where access to a protected operation is not restricted according to the intended security policy. The insecure pattern is exposing a high-impact administrative action through a request path whose authentication or authorization checks are missing, incomplete, or applied inconsistently.

Potential impact

  • An unauthenticated attacker may alter WAN or upstream provisioning settings
  • Network connectivity could be disrupted or redirected
  • Router administration or dependent services may become unavailable
  • Traffic could be exposed to unauthorized infrastructure if configuration changes are accepted
  • The device could be used as a foothold for further attacks against connected systems

General mitigation guidance

Mitigation generally focuses on enforcing authorization at the point where sensitive WAN configuration changes are performed.

Common defensive patterns include:

  • Require authenticated, authorized administrative sessions for every configuration-changing operation
  • Apply deny-by-default access controls to CGI handlers and management endpoints
  • Centralize authorization checks so individual functions cannot bypass them
  • Restrict management interfaces to trusted networks and administrative channels
  • Validate configuration changes and preserve secure defaults when requests are incomplete or malformed
  • Run management services with the minimum privileges needed to apply approved settings
  • Record and alert on unexpected changes to WAN configuration

How teams detect issues like this

Organizations can look for this issue through:

  • Static analysis rules that identify configuration-changing handlers lacking authorization checks
  • Code review signals such as direct state changes in CGI functions before authentication or privilege validation
  • Dynamic testing of management endpoints with unauthenticated and low-privilege requests
  • API and router policy checks requiring authentication for all administrative POST operations
  • Monitoring for unexpected WAN configuration changes, unusual provisioning values, or repeated requests to configuration endpoints

Automated security review tools may help identify missing access-control checks, but endpoint behavior should also be validated in an isolated test environment.

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 exploitable over the network when the router's CGI interface is reachable by an attacker. Exposure depends on management-interface configuration, network segmentation, and whether the endpoint is accessible from an untrusted network.

The reported issue allows unauthenticated attackers to invoke the affected configuration operation, although network reachability to the relevant service remains necessary.

Require authentication and explicit authorization before processing any WAN configuration change, and enforce those checks centrally and consistently across all management endpoints.

Use deny-by-default management policies, test administrative APIs with unauthenticated and low-privilege requests, restrict management exposure, and monitor configuration changes for unexpected activity.

Find out what's already
exploitable in your codebase.