/

CVE-2026-51729

Severity:

CRITICAL RISK

(9.1)

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

CVE-2026-51729

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Unauthorized device deletion and 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 vulnerability in the TOTOLINK T6 allows unauthenticated attackers to request deletion of a managed slave device through a crafted HTTP POST request. The issue becomes risky when the device management endpoint is reachable and does not require effective authentication or authorization checks.

Affected context

The vulnerability occurs in the TOTOLINK T6 management interface, specifically in the delDevice function handling requests to /cgi-bin/cstecgi.cgi. It may be present when the endpoint is exposed to an attacker and the device accepts deletion requests without adequately verifying the caller's identity and permissions.

Exploit preconditions

  • Attack surface: HTTP management interface at /cgi-bin/cstecgi.cgi
  • Required access: Network reachability to the affected management endpoint; authentication may not be required
  • Trigger point: A request processed by the delDevice function
  • Why exploitation is possible: The deletion operation does not consistently enforce authentication and authorization before acting on the requested managed device

Why this happens

The underlying defect is an authorization failure in a management operation. The delDevice function performs a security-sensitive deletion based on client input without establishing that the requester is authenticated and permitted to remove the selected device. This behavior maps to CWE-284, Improper Access Control, because the application fails to enforce an appropriate security policy around a protected administrative action.

Potential impact

  • An attacker may remove a managed slave device from the controller
  • Network services could become unavailable or degraded
  • Device-management relationships may be disrupted
  • Unauthorized changes could complicate monitoring, recovery, or incident response

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every sensitive

management operation rather than relying on endpoint visibility or client-side

controls.

Common defensive patterns include:

  • Requiring strong authentication for administrative interfaces and device-management actions
  • Enforcing server-side authorization checks for the specific device and operation
  • Validating that requested device identifiers belong to the authenticated administrative scope
  • Rejecting state-changing requests that lack appropriate authorization or anti-forgery protections
  • Limiting management-interface exposure to trusted networks and applying least privilege
  • Using secure-by-default policies that disable unnecessary remote administration
  • Recording and alerting on unexpected device deletion requests

How teams detect issues like this

Detection approaches may include:

  • Static analysis for state-changing handlers that lack centralized authentication or authorization checks
  • Code review of administrative endpoints and functions that delete or modify managed resources
  • Testing unauthenticated and lower-privilege requests against every management operation
  • Web and device logs monitoring requests to /cgi-bin/cstecgi.cgi, especially deletion actions
  • Policy enforcement requiring authorization middleware for destructive API routes
  • Automated security testing or neutral code-review tools that flag missing 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

It may be exploitable over the network when the affected management endpoint is

reachable. The practical scope depends on firewall rules, interface exposure,

and other deployment controls.

The reported behavior permits unauthenticated requests, so a valid account may

not be required when an attacker can reach the vulnerable endpoint.

Require server-side authentication and authorization before processing device

deletion requests, and verify that the requested device is within the caller's

permitted administrative scope.

Apply centralized access-control middleware, test sensitive operations with

unauthenticated and low-privilege identities, restrict management interfaces,

and monitor destructive administrative actions.

Find out what's already
exploitable in your codebase.