CVE-2026-51754: Incorrect access control in the updateSlaveIpList function of TOTOLINK T6 4.1.5cu.748_B20211015 allows unau...
Incorrect access control in the updateSlaveIpList function of TOTOLINK T6 4.1.5cu.748_B20211015 allows unauthenticated attackers to overwrite the slave IP inventory state via sending a crafted MQTT message to the cs_broker component.
Security readout for executives and security teams
Plain-English summary
A flaw in the TOTOLINK T6 allows an unauthenticated attacker who can reach its MQTT broker component to overwrite the router’s slave IP inventory. The reported impact is potentially severe because the CVSS assessment indicates possible loss of confidentiality, integrity, and availability, although the supplied sources do not document observed real-world attacks.
Executive priority
Treat confirmed deployments as an urgent remediation item because exploitation reportedly requires neither credentials nor user interaction and carries a 9.8 score. Prioritize internet-accessible or broadly reachable devices first. Do not interpret critical severity alone as evidence that attacks are occurring.
Technical view
CVE-2026-51754 is an incorrect access-control vulnerability in updateSlaveIpList within the cs_broker component of TOTOLINK T6 firmware 4.1.5cu.748_B20211015. A crafted MQTT message can reportedly update slave IP inventory state without authentication. It is classified as CWE-284 and scored CVSS 3.1 9.8: network-accessible, low complexity, no privileges, and no user interaction.
Likely exposure
Exposure is most likely where a TOTOLINK T6 running the named firmware permits untrusted systems to communicate with cs_broker over MQTT. The supplied structured affected-product field is unspecified, so broader model or firmware impact cannot be established from this bundle.
Exploitation context
The supplied record describes a remotely reachable, unauthenticated attack condition, but provides no evidence of active exploitation. The CVE is not identified as being in KEV. Public proof-of-concept or exploitation maturity cannot be confirmed from the supplied evidence.
Researcher notes
The record names one firmware build and function but supplies no CPEs or normalized affected-product data. It also does not identify a patch, fixed version, vendor advisory, or active exploitation. Defensive validation should avoid sending crafted messages to production equipment; rely on inventory, configuration review, logging, and authorized lab testing.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-284 · source CWE mapping
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.