/

CVE-2026-51768

Severity:

HIGH RISK

(7.5)

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

CVE-2026-51768

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Unauthorized Modification of Privileged Network Configuration

Severity:

HIGH RISK

(7.5)

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 missing access control check in the setElinkQosConfig function of the TOTOLINK T6 allows unauthenticated attackers to change privileged QoS policies on the master device. The issue becomes risky when the cs_broker component accepts crafted MQTT messages without verifying authorization.

Affected context

The vulnerability affects TOTOLINK T6 deployments using firmware 4.1.5cu.748_B20211015, where the cs_broker component processes MQTT messages that reach setElinkQosConfig. Risk depends on whether the broker is reachable by an unauthenticated party and whether the function can modify QoS settings on the master device without an effective authorization check.

Exploit preconditions

  • Attack surface: The cs_broker MQTT message-processing interface
  • Required access: Ability to send MQTT messages to the reachable broker; authentication is not required according to the vulnerability description
  • Trigger point: Processing of a crafted message by setElinkQosConfig
  • Why exploitation is possible: The function does not adequately enforce authorization before applying privileged QoS policy changes

Why this happens

The underlying bug is an authorization failure in which a privileged configuration operation trusts an incoming MQTT request without confirming that the requester is permitted to perform the action. This maps to CWE-284: Improper Access Control, because access to a sensitive device management function is not restricted according to the required security policy.

Potential impact

  • An attacker may modify QoS policies on the master device.
  • Network traffic prioritization or bandwidth allocation could be altered.
  • Device performance or availability could be degraded.
  • Unauthorized configuration changes could support follow-on disruption or lateral activity.

General mitigation guidance

Mitigation generally centers on enforcing authorization at the function

boundary rather than trusting message reachability or broker routing alone.

Common defensive patterns include:

  • Require authenticated and authorized identities for privileged MQTT operations.
  • Apply explicit per-function authorization checks before changing QoS policy.
  • Use secure-by-default broker access controls, topic permissions, and transport protection.
  • Validate message structure and permitted policy values without treating validation as authorization.
  • Restrict management interfaces to trusted networks and apply least privilege to device services.
  • Record and review privileged configuration changes, including the initiating identity and source.

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis and code review rules that flag privileged handlers lacking authorization checks.
  • Review of MQTT topic permissions, broker exposure, and unauthenticated message paths.
  • Tests that submit configuration requests under anonymous or unauthorized identities.
  • Monitoring for unexpected QoS policy changes, unusual MQTT clients, and repeated rejected or malformed requests.
  • Policy enforcement requiring authentication and authorization for all device-management operations.

Automated security review tools may help identify externally reachable handlers that invoke sensitive configuration functions without 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

It may be remotely exploitable when the cs_broker MQTT interface is reachable by an

attacker and accepts messages without authentication or authorization.

No authenticated account is described as necessary. The critical prerequisite is the

ability to deliver a crafted MQTT message to the broker.

Enforce authentication and explicit authorization inside setElinkQosConfig before

applying any privileged QoS policy change, while also restricting broker exposure.

Treat every management message as untrusted, apply per-operation access controls,

limit MQTT topics by identity, use protected transport, and test anonymous and

low-privilege request paths during security reviews.

Find out what's already
exploitable in your codebase.