/

CVE-2026-51743

Severity:

CRITICAL RISK

(9.1)

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

CVE-2026-51743

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Guest Wi-Fi 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 flaw in the TOTOLINK T6 allows unauthenticated attackers to send a crafted MQTT message that disables guest virtual access point interfaces. The issue becomes risky when the device exposes the relevant MQTT broker or otherwise permits unauthenticated network access to the affected synchronization function.

Affected context

The vulnerability occurs in the guest_wifi_sync function and its interaction with the cs_broker MQTT component. It affects deployments where an attacker can reach the MQTT message-handling surface without authentication and where guest virtual AP state changes are accepted without sufficient authorization checks.

Exploit preconditions

  • Attack surface: The device's MQTT message-handling component
  • Required access: Network access sufficient to communicate with cs_broker; authentication is not required according to the vulnerability description
  • Trigger point: Processing of a crafted MQTT message by guest_wifi_sync
  • Why exploitation is possible: The function permits a guest virtual AP state change without verifying that the sender is authorized to perform that operation

Why this happens

The underlying bug is an authorization failure in a privileged device-management operation. The guest_wifi_sync function appears to trust incoming MQTT messages without enforcing an appropriate identity, role, or capability check before disabling guest virtual AP interfaces. This behavior maps to CWE-284: Improper Access Control, in which access to a protected resource or operation is not adequately restricted.

Potential impact

  • Guest Wi-Fi access may be disabled
  • Legitimate users may lose connectivity to guest virtual AP interfaces
  • Network availability and service continuity could be reduced
  • Repeated messages may cause persistent or recurring guest-network disruption
  • Administrative teams may face increased support and recovery activity

General mitigation guidance

Mitigation generally focuses on enforcing authorization at the point where MQTT messages are translated into device-management actions.

Common defensive patterns include:

  • Requiring authenticated and authorized MQTT clients for control operations
  • Applying topic-level and command-level access policies
  • Validating message origin, scope, and intended target before changing AP state
  • Separating read-only synchronization messages from privileged configuration actions
  • Restricting broker exposure to trusted management networks
  • Running network services with the minimum privileges required
  • Using secure-by-default guest-network behavior and safe recovery procedures

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis and code review checks for state-changing handlers without authorization gates
  • Review of MQTT topic permissions, client authentication, and command-to-privilege mappings
  • Network monitoring for unauthenticated MQTT traffic and unexpected guest AP state changes
  • Device logs or telemetry showing repeated guest virtual AP disable operations
  • Policy enforcement that limits management protocols to trusted interfaces and networks
  • Automated security review tools that flag externally controlled inputs reaching privileged configuration 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 exploitable over the network when the affected MQTT service is reachable and accepts unauthenticated messages. The practical scope depends on network exposure and device segmentation.

No authenticated account is described as necessary. An attacker needs network access to the cs_broker component and a way to reach the affected message-processing path.

Require strong client authentication and explicit authorization before processing any MQTT command that changes guest virtual AP state. Restrict broker access to trusted management networks as an additional layer.

Treat every externally supplied message as untrusted, enforce authorization at each privileged operation, apply least-privilege broker policies, and monitor for unexpected configuration changes.

Find out what's already
exploitable in your codebase.