/

CVE-2026-51718

Severity:

CRITICAL RISK

(9.8)

Access Control (CWE-284) in TOTOLINK T6 DHCP Rules

CVE-2026-51718

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Unauthorized Configuration Modification and Network Disruption

Severity:

CRITICAL RISK

(9.8)

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 attackers to remove static DHCP reservations through a crafted request to the router's CGI endpoint.

Successful exploitation may alter network address-assignment behavior, disrupt connected devices, and weaken local network availability without requiring valid credentials.

Affected context

The issue occurs in TOTOLINK T6 4.1.5cu.748_B20211015 deployments where the delStaticDhcpRules function is reachable through the router's web CGI interface. Risk is elevated when the management interface is accessible to untrusted network users and the endpoint does not enforce authentication or authorization before deleting static DHCP reservations.

Exploit preconditions

  • Attack surface: The router's HTTP CGI management interface
  • Required access: Network connectivity to the exposed management endpoint; valid credentials may not be required
  • Trigger point: Processing of a request handled by delStaticDhcpRules
  • Why exploitation is possible: The endpoint performs a sensitive configuration change without adequately verifying the caller's identity and permissions

Why this happens

The vulnerability results from incorrect access-control enforcement around a state-changing administrative operation. The affected function permits deletion of static DHCP reservations without establishing that the requester is authenticated and authorized to modify router configuration.

This maps to CWE-284: Improper Access Control, where a protected resource or operation is insufficiently restricted. The insecure pattern is exposing a privileged management action through a request handler that lacks consistent authentication and authorization checks.

Potential impact

  • An attacker may remove static DHCP reservations
  • Network-connected devices could receive unexpected addresses or lose predictable address assignments
  • Local services may become unavailable or difficult to reach
  • Network administration and troubleshooting could be disrupted
  • The change could support follow-on attacks against affected devices or services

General mitigation guidance

Mitigation generally focuses on ensuring that every configuration-changing endpoint requires strong authentication and explicit authorization.

Common defensive patterns include:

  • Applying centralized authentication and authorization checks to all administrative CGI handlers
  • Enforcing least privilege for individual configuration operations
  • Keeping management interfaces isolated from untrusted networks
  • Using secure-by-default settings that disable external management access where it is unnecessary
  • Validating request context and rejecting unauthenticated or unauthorized state-changing requests
  • Recording configuration changes and protecting audit records from tampering
  • Reducing input trust by accepting only narrowly defined, schema-validated management parameters

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis rules identifying state-changing handlers without authentication or authorization checks
  • Code review signals such as direct configuration mutation from CGI parameters
  • Tests that invoke administrative endpoints with missing, invalid, and lower-privilege sessions
  • Network monitoring for unauthenticated requests to management interfaces and unusual DHCP reservation deletions
  • Policy enforcement that prevents router administration interfaces from being exposed beyond trusted management networks

Automated security review tools may help identify missing access-control checks, but endpoint behavior should also be verified through authenticated and unauthenticated testing.

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 can be exploitable over the network when the router's CGI management interface is reachable by an attacker. Exposure depends on network segmentation and management-interface settings.

The described flaw allows unauthenticated access to the affected operation, so valid router credentials may not be required when the endpoint is reachable.

Require authentication and operation-specific authorization before processing any request that changes DHCP reservations or other administrative configuration.

Apply centralized access-control middleware, isolate management interfaces, test sensitive endpoints without credentials, and monitor configuration changes.

Find out what's already
exploitable in your codebase.