/

CVE-2026-51675

Severity:

CRITICAL RISK

(9.1)

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

CVE-2026-51675

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Unauthorized Network Configuration Changes

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 setWanIeCfg function of TOTOLINK T6 allows unauthenticated attackers to change uplink settings through a crafted HTTP POST request.

Because the affected management endpoint does not adequately verify authorization, attackers who can reach the device's web interface may alter network configuration without valid credentials.

Affected context

The vulnerability occurs in TOTOLINK T6 firmware 4.1.5cu.748_B20211015 when the device exposes the /cgi-bin/cstecgi.cgi management endpoint and routes requests to the setWanIeCfg function. Risk is increased when the administration interface is reachable from an untrusted network or when request authorization is not enforced consistently for WAN configuration operations.

Exploit preconditions

  • Attack surface: The device's HTTP-based management interface
  • Required access: Network reachability to /cgi-bin/cstecgi.cgi; valid authentication may not be required
  • Trigger point: A crafted POST request invoking the setWanIeCfg operation
  • Why exploitation is possible: The function permits sensitive uplink configuration changes without sufficiently verifying the caller's authorization

Why this happens

The underlying flaw is an authorization failure in a security-sensitive management operation. The setWanIeCfg function processes requests that modify WAN or uplink settings without applying an effective access-control check before the change is accepted. This behavior maps to CWE-284: Improper Access Control, where a component does not properly restrict access to a protected resource or operation.

Potential impact

  • An unauthenticated attacker could alter WAN or uplink settings
  • Network traffic could be redirected, disrupted, or intercepted
  • The device could lose connectivity or become difficult to administer
  • Malicious DNS, gateway, or routing values could affect connected users
  • The router could be used to support follow-on attacks against internal systems

General mitigation guidance

Mitigation generally focuses on enforcing authorization at the server-side handler and protecting all network-configuration operations by default.

Common defensive patterns include:

  • Require authenticated, authorized administrative sessions before processing WAN changes
  • Apply centralized authorization checks consistently across management endpoints
  • Restrict management interfaces to trusted networks or dedicated administration paths
  • Validate submitted configuration values against strict schemas and safe ranges
  • Use least-privilege service accounts and separate read-only from configuration capabilities
  • Add anti-CSRF protections and secure session controls for browser-based administration
  • Log and alert on unauthorized or unusual changes to uplink settings

How teams detect issues like this

Organizations can assess for this class of issue through:

  • Static analysis and code review rules that identify state-changing handlers without authorization checks
  • Testing each management endpoint with authenticated, unauthenticated, and lower-privilege sessions
  • API inventory reviews that map sensitive operations to explicit authorization policies
  • Network monitoring for unexpected POST requests to router configuration endpoints
  • Audit-log review for WAN, DNS, gateway, and routing changes that lack a corresponding administrative action
  • Policy enforcement requiring authorization and CSRF controls for all browser-accessible state changes

Automated security testing tools may help identify exposed management operations, but endpoint-specific authorization review remains important.

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 TOTOLINK T6 management interface is reachable by an attacker. Direct internet exposure is not required if an attacker has access to the same local network.

The vulnerability description indicates that authentication may not be required. Network reachability to the affected management endpoint is the primary access condition.

Require a valid, authorized administrative session before allowing setWanIeCfg or any equivalent operation to modify uplink settings. Authorization should be enforced server-side rather than inferred from client-provided parameters.

Maintain an explicit authorization policy for every state-changing endpoint, test operations across privilege levels, restrict management interfaces to trusted networks, and monitor configuration changes.

Find out what's already
exploitable in your codebase.