/

CVE-2026-51646

Severity:

CRITICAL RISK

(9.1)

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

CVE-2026-51646

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Unauthorized disclosure of parental-control configuration

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 broken access-control vulnerability in the TOTOLINK T6 allows unauthenticated requests to retrieve parental-control rules through the getParentalRules function. The issue becomes risky when the router exposes the affected management endpoint to a network where untrusted users can send requests.

Affected context

The vulnerability occurs in TOTOLINK T6 firmware 4.1.5cu.748_B20211015 when the router processes requests to /cgi-bin/cstecgi.cgi and invokes the getParentalRules function without adequately enforcing authentication or authorization. Exposure depends on network reachability of the router's web-management interface and the deployment's access controls.

Exploit preconditions

  • Attack surface: The router's HTTP management interface and CGI request handler
  • Required access: Network connectivity to the affected endpoint; authentication may not be required
  • Trigger point: Processing of a request that invokes getParentalRules
  • Why exploitation is possible: The function does not properly verify whether the requester is authorized to retrieve parental-control rules

Why this happens

The underlying flaw is an authorization failure in an administrative data-retrieval function. Access control checks are missing, incomplete, or applied inconsistently before sensitive parental-control rules are returned, mapping to CWE-284: Improper Access Control. The insecure pattern is exposing management data through an endpoint without enforcing authentication and object-level authorization at the point of access.

Potential impact

  • An unauthenticated attacker may read parental-control rules
  • Attackers could infer household policies, schedules, or restricted destinations
  • Disclosed configuration data may aid further attacks against the router or connected users
  • Privacy and confidentiality of household network settings may be reduced

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every administrative data access boundary.

Common defensive patterns include:

  • Requiring authentication before processing management and diagnostic requests
  • Enforcing explicit authorization checks within the handler that returns parental-control data
  • Applying least-privilege access to configuration and administrative APIs
  • Limiting management interfaces to trusted networks or secured administration channels
  • Returning only the minimum data needed for an authorized operation
  • Using secure-by-default management settings that do not expose administrative endpoints broadly
  • Reducing trust in client-supplied operation names and validating requested resources server-side

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis and code review checks for administrative handlers lacking authentication or authorization guards
  • Tests that access each management operation with anonymous and low-privilege sessions
  • API inventory reviews confirming that sensitive CGI actions require explicit policy enforcement
  • Network monitoring for unauthenticated requests to router management endpoints
  • Policy checks that restrict management interfaces to approved administrative networks
  • Automated security testing tools that assess authentication and authorization coverage across exposed handlers

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 router's management interface and affected CGI endpoint are reachable by an untrusted party.

The reported issue allows unauthenticated attackers to request parental-control rules, so a valid account may not be required. Network reachability remains necessary.

Require authentication and enforce authorization directly within the function that retrieves parental-control data, while limiting management access to trusted networks.

Maintain an inventory of administrative endpoints, apply centralized and per-function authorization checks, and test every sensitive operation with anonymous and lower-privilege identities.

Find out what's already
exploitable in your codebase.