/

CVE-2026-51720

Severity:

CRITICAL RISK

(9.1)

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

CVE-2026-51720

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Unauthorized Firewall Rule Modification

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 allows unauthenticated requests to remove firewall filter rules. When the affected management endpoint accepts a crafted request without adequately verifying authorization, an attacker may weaken network filtering and expose protected services.

Affected context

The issue occurs in TOTOLINK T6 firmware when the delIpPortFilterRules function is reachable through the router's CGI interface and does not sufficiently enforce authentication or authorization. Risk depends on whether the management interface is accessible from an attacker-controlled network and whether firewall filtering is relied upon to protect internal services.

Exploit preconditions

  • Attack surface: The router's CGI management interface, specifically the firewall-rule deletion functionality
  • Required access: Network reachability to the affected HTTP endpoint; valid credentials may not be required
  • Trigger point: Processing of a crafted POST request handled by delIpPortFilterRules
  • Why exploitation is possible: The function may perform a security-sensitive rule deletion operation without adequately confirming the caller's authorization

Why this happens

The underlying bug is an authorization failure in a security-sensitive administrative operation. The endpoint exposes functionality that changes firewall policy but does not consistently enforce an appropriate authentication and authorization decision before processing the request. This behavior maps to CWE-284: Improper Access Control, because access restrictions do not reliably protect a privileged resource or operation.

Potential impact

  • An attacker may remove firewall rules that restrict inbound or outbound traffic
  • Protected router services or internal hosts could become more reachable
  • Network segmentation and filtering controls could be weakened
  • Unauthorized access to exposed services may become easier
  • The router's security posture could be degraded without an administrator's approval

General mitigation guidance

Mitigation generally focuses on ensuring that every firewall-policy modification is protected by strong, explicit authorization checks.

Common defensive patterns include:

  • Requiring authenticated administrative sessions for all rule-management operations
  • Enforcing server-side authorization rather than relying on client-visible state
  • Applying deny-by-default controls to management endpoints
  • Validating the requested operation against the authenticated administrator's privileges
  • Restricting management interfaces to trusted networks or dedicated administration paths
  • Preserving firewall protections when authorization checks fail or requests are malformed
  • Using least-privilege service identities and minimizing exposed router management functionality

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis and endpoint inventories that identify unauthenticated handlers performing configuration changes
  • Code review checks for missing authentication and authorization gates around firewall-rule operations
  • Dynamic testing that verifies administrative endpoints reject unauthenticated and unauthorized state-changing requests
  • Web-server and router logs showing unexpected POST requests or firewall-rule deletions
  • Policy enforcement requiring management interfaces to use authenticated, restricted administrative channels
  • Automated security testing tools that exercise access-control decisions across privileged API functions

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 management CGI interface is reachable by an attacker. Exposure depends on network topology, administrative access policies, and whether the interface is restricted to trusted networks.

The vulnerability description indicates that authentication may not be required for the affected operation. The practical scope still depends on endpoint exposure and deployment configuration.

Ensure the firewall-rule deletion operation requires an authenticated session and an explicit authorization check before any state change occurs. Restricting management access to trusted administration networks provides an additional layer of defense.

Apply centralized authorization middleware to all state-changing management endpoints, test unauthenticated and low-privilege access paths, log security-sensitive configuration changes, and enforce deny-by-default management policies.

Find out what's already
exploitable in your codebase.