/

CVE-2026-51679

Severity:

CRITICAL RISK

(9.1)

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

CVE-2026-51679

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Unauthorized Administrative Access

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 users to change the administrator account password through a specially crafted web request.

Because authentication is not properly enforced for the affected password-configuration function, a remote attacker may gain administrative control of the router.

Affected context

The vulnerability occurs in the TOTOLINK T6 4.1.5cu.748_B20211015 web administration interface, specifically where the setPasswordCfg function processes requests associated with /cgi-bin/cstecgi.cgi. Risk is highest when the management interface is reachable by untrusted users or exposed beyond a trusted administrative network and the function does not consistently enforce authentication and authorization.

Exploit preconditions

  • Attack surface: The router's web administration service and its CGI request handler
  • Required access: Network reachability to the affected management endpoint; valid authentication may not be required
  • Trigger point: Processing of a password-configuration request by the setPasswordCfg function
  • Why exploitation is possible: The function permits a sensitive administrator-account change without adequately verifying that the requester is authorized to perform it

Why this happens

The underlying flaw is an authorization failure in a sensitive account-management operation. The application exposes a function capable of changing administrator credentials but does not reliably enforce authentication and authorization before applying the requested change. This behavior maps to CWE-284: Improper Access Control, where access restrictions are missing or incorrectly implemented for a protected resource or operation.

Potential impact

  • An unauthenticated attacker may change the administrator account credentials
  • An attacker could gain persistent administrative access to the router
  • Network configuration, traffic controls, or connected-device settings may be modified
  • The device could be used to redirect traffic, weaken network security, or support further attacks

General mitigation guidance

Mitigation generally focuses on ensuring that every administrator-account operation is protected by strong, server-side authorization checks.

Common defensive patterns include:

  • Require authenticated sessions and explicit administrative privileges before processing credential changes
  • Enforce authorization independently of client-supplied parameters or interface state
  • Apply consistent access-control checks across all CGI handlers and alternate request paths
  • Limit management interfaces to trusted networks and avoid exposing them directly to the internet
  • Require reauthentication or equivalent high-assurance confirmation for administrator credential changes
  • Follow least-privilege principles for management services and separate administrative functions from ordinary device operations

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis and code review checks for password-changing functions that lack centralized authorization enforcement
  • Review of CGI routes and handlers that modify administrator accounts or other security-sensitive settings
  • Tests verifying that unauthenticated, low-privilege, and cross-session requests cannot perform privileged operations
  • Web-server and router logs showing password-configuration requests without a preceding authenticated administrative session
  • Policy enforcement requiring centralized authentication middleware and negative authorization tests for management endpoints
  • Automated security testing tools that identify unauthenticated access to account-management functions

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 router's management interface is reachable by an attacker. Exploitability depends on network exposure and deployment controls.

The reported issue allows the affected administrator-account change without the expected authentication, so an existing account may not be required.

Ensure the password-configuration operation requires an authenticated session with explicit administrative authorization, enforced on the server before any state change occurs.

Centralize access-control checks, restrict management interfaces to trusted networks, and include unauthenticated and low-privilege authorization tests for every sensitive administrative endpoint.

Find out what's already
exploitable in your codebase.