/

CVE-2026-51670

Severity:

CRITICAL RISK

(9.8)

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

CVE-2026-51670

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Unauthorized information access and modification of upgrade state

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 flaw in the TOTOLINK T6 allows unauthenticated requests to reach the getSlaveUpdate function through the device's CGI interface. An attacker may query slave upgrade status and alter upgrade bookkeeping by sending a specially crafted POST request.

Affected context

The issue occurs in TOTOLINK T6 devices when the CGI request handler exposes the getSlaveUpdate function without adequately enforcing authentication or authorization. Deployments are most at risk when the management interface or relevant CGI endpoint is reachable by untrusted network users.

Exploit preconditions

  • Attack surface: The device's HTTP CGI interface at /cgi-bin/cstecgi.cgi
  • Required access: Network connectivity to the exposed management endpoint; valid authentication may not be required
  • Trigger point: A crafted POST request invoking the getSlaveUpdate function
  • Why exploitation is possible: The function performs upgrade-status and bookkeeping operations without sufficient access-control enforcement

Why this happens

The underlying bug is an authorization failure in a device management endpoint. The request handler permits unauthenticated callers to invoke functionality intended for controlled administrative use, allowing them to read upgrade-related state and influence bookkeeping. This behavior maps to CWE-284: Improper Access Control, in which security-relevant operations are not consistently restricted to authorized principals.

Potential impact

  • An attacker could obtain information about slave-device upgrade status
  • An attacker could alter upgrade bookkeeping or device-management state
  • Monitoring and operational decisions could be based on inaccurate upgrade information
  • The flaw could support further attacks if modified state affects other administrative workflows

General mitigation guidance

Mitigation generally focuses on enforcing authorization at the function and operation level rather than relying only on interface exposure or client behavior.

Common defensive patterns include:

  • Requiring authentication and explicit authorization before processing upgrade-status requests
  • Applying deny-by-default access controls to administrative CGI functions
  • Separating read-only status queries from state-changing bookkeeping operations
  • Validating request parameters and restricting state transitions to expected administrative workflows
  • Limiting management interfaces to trusted networks and applying least privilege to device-management services
  • Recording and reviewing security-relevant state changes

How teams detect issues like this

Organizations can look for this issue through:

  • Static analysis and code review of CGI dispatch tables and authorization checks
  • Searches for administrative functions reachable before authentication or privilege validation
  • Tests that invoke management endpoints with missing, invalid, and low-privilege credentials
  • Web-server and device logs showing repeated POST requests to /cgi-bin/cstecgi.cgi or unexpected upgrade-state changes
  • Policy enforcement requiring authentication and authorization controls for all state-changing management operations

Automated security review tools may help identify exposed administrative handlers, but endpoint-specific testing is also important.

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 device's management CGI interface is reachable by an attacker. The practical scope depends on network exposure and administrative-interface restrictions.

The described flaw allows unauthenticated attackers to invoke the affected function, so valid device credentials may not be required when the endpoint is accessible.

Require authentication and function-level authorization before allowing access to upgrade status or bookkeeping operations, while separating read-only actions from state changes.

Use deny-by-default management interfaces, test every administrative endpoint across privilege levels, restrict management access to trusted networks, and monitor unexpected state changes.

Find out what's already
exploitable in your codebase.