/

CVE-2026-51710

Severity:

CRITICAL RISK

(9.1)

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

CVE-2026-51710

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Unauthorized Modification of Security and Access-Control Settings

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 flaw in the TOTOLINK T6 router's setParentalRules function allows unauthenticated users to change parental-control settings.

An attacker who can reach the device's web interface may send a specially crafted POST request to alter these controls without first proving authorization.

Affected context

The vulnerability affects TOTOLINK T6 routers running firmware version 4.1.5cu.748_B20211015 when the setParentalRules function is accessible through the device's CGI interface. The risk is greatest where the management interface is reachable by untrusted users or exposed beyond a trusted administrative network.

Exploit preconditions

  • Attack surface: The router's CGI-based web management interface
  • Required access: Network connectivity to the affected management endpoint; authentication may not be required
  • Trigger point: Processing of a POST request handled by setParentalRules
  • Why exploitation is possible: The function does not adequately enforce authorization before accepting changes to parental-control behavior

Why this happens

The underlying flaw is an authorization failure in a state-changing administrative function. The application accepts requests that modify parental-control settings without reliably verifying that the requester has the required privileges. This behavior maps to CWE-284: Improper Access Control, in which access restrictions are missing, incorrectly applied, or bypassable for a protected operation.

Potential impact

  • An unauthenticated attacker could alter parental-control policies
  • Network users may gain access to content or services intended to be restricted
  • Administrators could lose confidence in the router's policy enforcement
  • The device's security configuration could be modified without authorization
  • Changes could support follow-on abuse of connected users or devices

General mitigation guidance

Mitigation generally focuses on enforcing authorization consistently for every state-changing management operation.

Common defensive patterns include:

  • Requiring authenticated, appropriately privileged sessions before processing administrative changes
  • Applying server-side authorization checks independently of client-side controls
  • Rejecting requests when session, role, or ownership context is absent or invalid
  • Restricting management interfaces to trusted administration networks
  • Using secure-by-default parental-control policies and preserving them when validation fails
  • Running management services with only the privileges required for their functions

How teams detect issues like this

Organizations can look for access-control weaknesses through:

  • Static analysis of CGI handlers and route-to-function mappings for missing authorization checks
  • Code review signals such as state-changing operations that do not invoke centralized access-control middleware
  • Dynamic testing that compares authenticated and unauthenticated behavior for administrative endpoints
  • Web-server and router logs showing policy changes without a corresponding valid administrative session
  • Policy enforcement requiring authentication and authorization for all configuration-modification endpoints

Automated application-security review tools may help identify missing checks, but endpoint behavior should also be verified in representative deployments.

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 is reachable by an attacker. Exposure depends on deployment and network-access controls.

The description indicates that authentication is not required for the affected operation, although network access to the relevant interface is still necessary.

Require a valid authenticated session and verify the caller's authorization on the server before allowing any parental-control changes.

Use centralized authorization middleware, test every state-changing endpoint without credentials and with lower-privileged accounts, and limit administrative interfaces to trusted networks.

Find out what's already
exploitable in your codebase.