CVE-2026-51729: Incorrect access control in the delDevice function of TOTOLINK T6 4.1.5cu.748_B20211015 allows unauthentica...
Incorrect access control in the delDevice function of TOTOLINK T6 4.1.5cu.748_B20211015 allows unauthenticated attackers to request deletion of a managed slave device via sending a crafted POST request to /cgi-bin/cstecgi.cgi.
Security readout for executives and security teams
Plain-English summary
A flaw in TOTOLINK T6 firmware 4.1.5cu.748_B20211015 reportedly lets an unauthenticated network attacker request removal of a managed slave device. This could undermine network administration and device configuration integrity. The supplied sources do not identify other affected versions or confirm a vendor fix.
Executive priority
Treat confirmed affected and untrusted-reachable devices as an immediate remediation priority. Quickly inventory, isolate management access, and seek vendor guidance. Prioritize exposed administrative interfaces, but avoid claiming an active campaign because the supplied evidence does not establish exploitation in the wild.
Technical view
The delDevice function exposed through /cgi-bin/cstecgi.cgi has incorrect access control (CWE-284). A crafted POST request can trigger managed slave-device deletion without authentication. CVSS 3.1 rates it 9.1: network-accessible, low complexity, requiring neither privileges nor user interaction. The sources do not explain the score's claimed high confidentiality impact.
Likely exposure
Exposure is limited to TOTOLINK T6 devices running the specifically reported firmware where the affected management endpoint is reachable by an attacker. The bundle provides no CPE mapping, deployment prevalence, default exposure details, or evidence that other firmware versions are affected.
Exploitation context
The CVSS vector indicates remote, low-complexity exploitation without credentials or user interaction. However, the CVE is not listed as KEV, and the supplied sources provide no evidence of active exploitation, public weaponization, or exploitation at scale.
Researcher notes
The record identifies one firmware build and one affected function, but supplies no patch status, vulnerable-version range, CPE, or technical root-cause detail. The described deletion behavior does not by itself explain the CVSS vector's high confidentiality impact. Validation should remain non-destructive and focus on version, reachability, controls, and telemetry.
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
5Source 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.