/

CVE-2026-51636

Severity:

CRITICAL RISK

(9.1)

Broken Access Control (CWE-284) in TOTOLINK T6 Wi-Fi ACL

CVE-2026-51636

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Unauthorized disclosure of Wi-Fi access-control rules

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 retrieve Wi-Fi access-control list rules through a crafted POST request.

The issue becomes risky when the management CGI endpoint is reachable and does not require authentication before processing the ACL retrieval operation.

Affected context

The vulnerability occurs in the TOTOLINK T6 4.1.5cu.748_B20211015 firmware, specifically in the getWiFiAclRules function exposed through /cgi-bin/cstecgi.cgi. Risk is higher when the device's management interface or CGI endpoint is reachable by untrusted users or networks and access checks are not consistently applied to the requested operation.

Exploit preconditions

  • Attack surface: The device's HTTP CGI management interface
  • Required access: No authentication is required according to the reported issue
  • Trigger point: A crafted POST request targeting the getWiFiAclRules operation
  • Why exploitation is possible: The function permits retrieval of Wi-Fi ACL rules without enforcing appropriate authorization checks

Why this happens

The underlying bug is an authorization failure in which a sensitive management operation can be invoked without verifying that the requester has permission to access it. This maps to CWE-284: Improper Access Control, because the application does not reliably enforce the intended security policy before returning Wi-Fi ACL data.

Potential impact

  • An attacker may obtain configured Wi-Fi ACL rules
  • Network access-control information could be exposed
  • The disclosed rules could help an attacker identify trusted or blocked devices
  • Information from the response could support further attacks against the router or connected network

General mitigation guidance

Mitigation generally focuses on enforcing authorization consistently for every management operation, including read-only functions.

Common defensive patterns include:

  • Requiring authenticated and appropriately authorized sessions for ACL retrieval
  • Applying centralized access-control checks before dispatching CGI actions
  • Denying access by default when authentication or authorization state is missing
  • Restricting management interfaces to trusted administrative networks
  • Limiting the sensitivity and detail of information returned to unauthorized callers
  • Running security tests that verify unauthenticated requests cannot invoke privileged operations

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis and code review checks for sensitive handlers lacking authorization guards
  • Review of CGI dispatch logic, especially operation names mapped directly from request data
  • Dynamic testing of management endpoints with missing, invalid, and low-privilege credentials
  • Web-server and router logs showing repeated POST requests to CGI operations from untrusted sources
  • Policy enforcement requiring authentication and authorization coverage for every administrative API action
  • Automated security review tools that identify exposed sensitive operations and inconsistent access 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 remotely exploitable when the router's CGI management endpoint is reachable by an attacker. Exposure depends on network configuration, interface binding, and any perimeter controls.

No authenticated account is required according to the vulnerability description. The attacker only needs network access to the affected endpoint.

Require authentication and enforce authorization before executing the getWiFiAclRules operation or returning its data.

Apply centralized deny-by-default access controls to all management APIs, restrict administrative interfaces to trusted networks, and test each sensitive operation with unauthenticated and low-privilege requests.

Find out what's already
exploitable in your codebase.