/

CVE-2026-51719

Severity:

HIGH RISK

(7.5)

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

CVE-2026-51719

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Unauthorized Security Policy Modification

Severity:

HIGH RISK

(7.5)

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 router allows unauthenticated users to remove URL filtering rules through a crafted HTTP request. The issue becomes risky when the affected management endpoint is reachable and fails to verify authorization before changing filtering policy.

Affected context

This vulnerability occurs in the TOTOLINK T6 4.1.5cu.748_B20211015 web management interface, specifically in the URL filtering rule removal functionality. Risk depends on exposure of the affected CGI endpoint and whether network controls, authentication boundaries, or administrative access restrictions limit requests to router management services.

Exploit preconditions

  • Attack surface: The router's HTTP management interface and CGI request handler
  • Required access: Network reachability to the affected endpoint; valid authentication may not be required
  • Trigger point: Processing of a request handled by the delUrlFilterRules function
  • Why exploitation is possible: The function does not adequately enforce authorization before allowing URL filtering rules to be removed

Why this happens

The underlying flaw is an authorization failure in a state-changing management function. The request handler performs a privileged operation without reliably confirming that the caller has the required administrative authority, mapping to CWE-284: Improper Access Control. This reflects an insecure pattern in which endpoint reachability or request formatting is treated as sufficient permission to modify security-related configuration.

Potential impact

  • An unauthenticated attacker may remove URL filtering rules
  • Internet access restrictions or content controls could be weakened
  • Protected users or devices may gain access to blocked destinations
  • Security policy integrity could be reduced without administrator awareness
  • The router's intended access-control posture could be undermined

General mitigation guidance

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

Common defensive patterns include:

  • Requiring authenticated, sufficiently privileged sessions for configuration changes
  • Applying centralized authorization checks at the management API boundary
  • Validating request ownership and target resources before performing deletion
  • Disabling or isolating administrative interfaces from untrusted networks
  • Using least-privilege service roles and secure-by-default management exposure
  • Recording and monitoring changes to URL filtering and related security policies

How teams detect issues like this

Organizations can assess this class of issue through:

  • Static analysis for state-changing handlers that lack authorization checks
  • Code review of CGI functions that add, modify, or delete security configuration
  • Tests that attempt privileged operations with unauthenticated and low-privilege sessions
  • API policy enforcement requiring authentication and authorization on management endpoints
  • Monitoring logs for unexpected deletion of URL filtering rules or configuration changes

Neutral automated security review tools may help identify management functions whose authorization checks are missing, inconsistent, or applied after the state-changing operation.

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 attacker. Exposure depends on deployment topology and administrative interface restrictions.

The described issue permits unauthenticated access to the affected operation, so a valid administrative session may not be required when the endpoint is accessible.

Enforce authentication and explicit authorization before every URL filtering rule deletion, using centralized access-control checks that cannot be bypassed by direct requests.

Apply deny-by-default management policies, test privileged endpoints with unauthenticated and low-privilege identities, restrict administrative network exposure, and audit security-configuration changes.

Find out what's already
exploitable in your codebase.