/

CVE-2026-51717

Severity:

CRITICAL RISK

(9.1)

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

CVE-2026-51717

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Unauthorized Device Configuration Change

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 allows unauthenticated attackers to change the device's operating mode through the setOpModeCfg function.

The issue becomes risky when the device exposes the affected CGI endpoint and does not require authentication before accepting the crafted POST request.

Affected context

The vulnerability occurs in TOTOLINK T6 firmware version 4.1.5cu.748_B20211015 when the device processes requests to /cgi-bin/cstecgi.cgi. The affected setOpModeCfg function appears to permit operating-mode changes without adequately verifying the requester's authorization.

Exploit preconditions

  • Attack surface: The device's HTTP/CGI management interface
  • Required access: Network reachability to the affected endpoint; authentication is not required according to the vulnerability description
  • Trigger point: A crafted POST request processed by setOpModeCfg
  • Why exploitation is possible: The function does not enforce appropriate access control before applying the requested operating-mode change

Why this happens

The underlying flaw is an authorization failure in a management operation. The setOpModeCfg function accepts a request that can alter device state without first establishing that the requester is permitted to perform that action. This behavior maps to CWE-284: Improper Access Control, where protected functionality is not adequately restricted to authorized users or contexts.

Potential impact

  • An unauthenticated attacker may change the device's operating mode
  • Network connectivity or routing behavior could be disrupted
  • The device may become misconfigured or unavailable
  • An attacker could use the altered mode as a stepping stone for further network attacks

General mitigation guidance

Mitigation generally focuses on enforcing authorization consistently across every device-management operation.

Common defensive patterns include:

  • Require authentication and authorization before processing operating-mode changes
  • Apply deny-by-default access policies to administrative CGI functions
  • Validate requests server-side rather than relying on client-side controls
  • Restrict management interfaces to trusted administrative networks
  • Run management services with only the privileges needed for configuration tasks
  • Log and alert on unauthorized or unexpected operating-mode changes

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis and review rules that identify state-changing endpoints without authorization checks
  • Code review signals showing direct configuration updates before identity and permission validation
  • Tests that submit administrative requests without credentials and verify that they are rejected
  • Network monitoring for unexpected POST requests to /cgi-bin/cstecgi.cgi
  • Policy enforcement requiring authentication and authorization middleware for all management operations

Automated security review tools may help identify missing access-control checks, but endpoint-level testing 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

Yes, it may be exploitable by an unauthenticated attacker who can reach the affected CGI endpoint over the network.

The attacker needs network connectivity to the device's management interface. The described issue does not require prior authentication.

Require authentication and explicit authorization before allowing any request to change the device's operating mode.

Use centralized access-control checks for all administrative endpoints, apply deny-by-default policies, restrict management exposure, and test unauthenticated state-changing requests.

Find out what's already
exploitable in your codebase.