/

CVE-2026-51751

Severity:

CRITICAL RISK

(9.8)

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

CVE-2026-51751

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Unauthorized mesh-management changes and denial of service

Severity:

CRITICAL RISK

(9.8)

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 send crafted MQTT messages to the cs_broker component. Under deployments where the broker accepts these messages without adequate authorization, an attacker may remove a selected slave device from local mesh management data and reboot the system.

Affected context

The vulnerability occurs in the TOTOLINK T6 mesh-management path, specifically where the delSlaveDevice function processes MQTT requests through the cs_broker component. Risk is increased when MQTT messages can reach this functionality without authentication or authorization checks and when management operations are exposed beyond trusted administrative boundaries.

Exploit preconditions

  • Attack surface: MQTT messages handled by the device's cs_broker component
  • Required access: Network reachability to the relevant MQTT service; authentication may not be required
  • Trigger point: Processing of a crafted message invoking the slave-device removal operation
  • Why exploitation is possible: The management function does not adequately verify whether the requester is authorized to remove mesh devices or initiate the associated reboot behavior

Why this happens

The underlying issue is improper access control, mapped to CWE-284. A privileged mesh-management operation is reachable through a message-handling interface without consistently enforcing authentication, authorization, and operation-specific validation. This insecure pattern treats a remotely supplied command as trusted instead of binding it to a verified administrative identity and permitted device-management scope.

Potential impact

  • An unauthenticated attacker could remove a specified slave device from local mesh-management data.
  • The device could be rebooted unexpectedly, causing service interruption.
  • Mesh availability and topology integrity may be disrupted.
  • Repeated requests could cause sustained denial of service or administrative instability.
  • Connected users may lose reliable access to network services.

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every management-operation entry point and reducing exposure of device-control interfaces.

Common defensive patterns include:

  • Require authenticated, authorized identities for MQTT management actions.
  • Apply operation-specific authorization so users can modify only permitted mesh devices.
  • Restrict broker listeners to trusted management networks and isolate them from untrusted clients.
  • Validate message structure, target identifiers, and operation state before performing changes.
  • Use secure-by-default broker policies that deny unauthenticated publishing and subscription.
  • Limit the device's management privileges and add safeguards around disruptive actions such as rebooting.
  • Log and rate-limit sensitive management operations for accountability and abuse resistance.

How teams detect issues like this

Organizations can identify similar weaknesses through:

  • Static analysis and code review checks for management handlers lacking authentication or authorization gates.
  • Inspection of MQTT topic and command mappings for unauthenticated publish access.
  • Tests that invoke administrative operations with missing, invalid, or mismatched identities.
  • Policy enforcement requiring deny-by-default broker ACLs and protected management networks.
  • Monitoring for unexpected device-removal events, repeated reboot requests, and unauthenticated MQTT activity.
  • Automated security review tools that flag externally reachable functions performing state changes without access-control checks.

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 remotely exploitable when an attacker can reach the relevant MQTT service and the broker permits the management message without sufficient authorization.

The described weakness allows unauthenticated attackers to reach the operation, although network exposure and broker configuration determine practical reachability.

Protect the MQTT management interface with authentication, deny-by-default broker permissions, and operation-specific authorization before any mesh state change or reboot is performed.

Treat all broker messages as untrusted, enforce authorization at each state-changing handler, isolate management services, validate command targets, and monitor sensitive administrative actions.

Find out what's already
exploitable in your codebase.