/

CVE-2026-51726

Severity:

CRITICAL RISK

(9.1)

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

CVE-2026-51726

Deferred

Vulnerability type

Category:

Incorrect Access Control

CWE:

CWE-284

Impact:

Unauthorized Modification of 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 requests to remove parental-control rules through the delParentalRules function.

An attacker who can reach the device's CGI interface may submit a crafted POST request, potentially disabling restrictions without valid credentials.

Affected context

The issue occurs in TOTOLINK T6 firmware 4.1.5cu.748_B20211015 when the parental-control management endpoint is reachable and the delParentalRules function does not adequately enforce authentication or authorization. Risk is higher when the router administration interface or its CGI endpoints are exposed to untrusted networks.

Exploit preconditions

  • Attack surface: The router's HTTP CGI interface at /cgi-bin/cstecgi.cgi
  • Required access: Network connectivity to the affected endpoint; valid credentials may not be required
  • Trigger point: Processing of a crafted POST request targeting the parental-rule deletion functionality
  • Why exploitation is possible: The deletion operation can be reached without an effective authorization check

Why this happens

The vulnerability results from an access-control failure in the delParentalRules function. The application performs a state-changing administrative operation without reliably verifying that the requester is authenticated and authorized to manage the targeted parental-control rules. This behavior maps to CWE-284: Improper Access Control, where protected functionality is exposed without adequate enforcement of the intended security policy.

Potential impact

  • An unauthenticated attacker may remove parental-control rules
  • Network restrictions for managed devices could be disabled
  • Users may lose expected content or time-based protections
  • The router's administrative control model could be weakened
  • Repeated unauthorized changes could reduce trust in device policy enforcement

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every state-changing administrative operation and reducing exposure of management interfaces.

Common defensive patterns include:

  • Requiring authentication and explicit authorization before processing rule-deletion requests
  • Binding authorization checks to the specific device, account, and rule being modified
  • Restricting administrative CGI endpoints to trusted management networks
  • Using secure session validation and request-integrity protections for state-changing actions
  • Applying least privilege to management services and separating administrative functions from general network access
  • Failing closed when authentication, authorization, or request validation cannot be confirmed

How teams detect issues like this

Organizations can assess for this class of issue through:

  • Static analysis checks for state-changing handlers that lack authentication or authorization gates
  • Code review of CGI dispatch logic and administrative operations
  • Tests that invoke management endpoints with no session, expired sessions, and unauthorized accounts
  • Network monitoring for unexpected POST requests to router administration paths
  • Policy enforcement requiring authentication and authorization coverage for every administrative API action

Automated security review tools may help identify externally reachable handlers that modify configuration without corresponding 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 CGI interface is reachable by an attacker. The practical scope depends on management-interface exposure and network segmentation.

The described behavior indicates that valid authentication may not be required. Network access to the vulnerable endpoint is the key prerequisite.

Enforce authentication and object-level authorization before allowing any parental-control rule to be deleted, and restrict management endpoints to trusted networks.

Apply centralized authorization checks to every state-changing administrative handler, test unauthenticated and unauthorized access paths, and monitor policy-management endpoints for anomalous activity.

Find out what's already
exploitable in your codebase.