/

CVE-2026-51722

Severity:

CRITICAL RISK

(9.1)

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

CVE-2026-51722

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Unauthorized network configuration changes, traffic exposure, and service disruption

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 Wi-Fi repeater configuration.

By reaching the affected configuration function, an attacker may redirect the device to an upstream wireless network they control, potentially exposing connected traffic or disrupting network access.

Affected context

The issue occurs in TOTOLINK T6 firmware when the repeater configuration function accepts requests without adequately verifying the caller's authorization. It is relevant to deployments where the device management interface or its CGI endpoint is reachable by an attacker and the repeater configuration can be changed without an authenticated administrative session.

Exploit preconditions

  • Attack surface: The device's web management CGI interface
  • Required access: Network reachability to the affected endpoint; authentication is not required
  • Trigger point: Processing of a request handled by the setWiFiRepeaterCfg function
  • Why exploitation is possible: The function permits sensitive upstream Wi-Fi settings to be changed without enforcing appropriate access control

Why this happens

The underlying defect is an authorization failure in a sensitive configuration operation. The setWiFiRepeaterCfg function changes network connectivity settings but does not consistently require or validate an authenticated, authorized administrative context before applying the request. This maps to CWE-284: Improper Access Control, where access restrictions are missing or insufficient for a protected resource or operation.

Potential impact

  • An attacker may redirect the repeater to an attacker-controlled upstream wireless network
  • Connected users' traffic could be exposed, observed, or manipulated depending on protocol protections
  • The device may lose connectivity or provide unreliable network service
  • The attacker could gain a position for further attacks against connected devices
  • Network administrators may experience unauthorized configuration changes

General mitigation guidance

Mitigation generally focuses on protecting every network-management operation with explicit authorization checks and reducing the exposure of administrative interfaces.

Common defensive patterns include:

  • Require authenticated administrative sessions for all repeater and wireless configuration changes
  • Enforce authorization at the endpoint and function level rather than relying only on interface visibility
  • Use secure-by-default management-plane settings, including restricted network exposure
  • Apply anti-request-forgery protections and validate session state for state-changing operations
  • Limit administrative privileges and separate configuration permissions from read-only access
  • Log and alert on changes to upstream network settings

How teams detect issues like this

Organizations can look for this weakness through:

  • Static analysis and code review of CGI handlers that modify network configuration
  • Review signals showing sensitive setters without nearby authentication and authorization checks
  • Dynamic testing of management endpoints using unauthenticated and low-privilege sessions
  • Monitoring for unexpected changes to repeater SSIDs, upstream addresses, or wireless credentials
  • Policy enforcement requiring authentication, authorization, and request-integrity checks for state-changing administrative APIs

Automated security review tools may help identify externally reachable configuration functions that lack access-control enforcement.

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, when the affected management CGI endpoint is reachable over a network. The request does not require prior authentication according to the vulnerability description.

The attacker needs network connectivity to the device's management interface. Physical access is not inherently required, although network segmentation may limit reachability.

Require authenticated and authorized administrative sessions before allowing any repeater or upstream Wi-Fi configuration change, and protect state-changing requests against forgery.

Apply centralized access-control middleware, review every configuration-changing endpoint, minimize management-plane exposure, and monitor for unauthorized network-setting changes.

Find out what's already
exploitable in your codebase.