/

CVE-2026-51694

Severity:

HIGH RISK

(7.5)

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

CVE-2026-51694

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Unauthorized Network Configuration 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

TOTOLINK T6 contains an incorrect access-control implementation in the

setStaticDhcpRules function. An unauthenticated attacker may be able to add

or modify static DHCP rules by submitting a crafted request to the router's

CGI endpoint.

Affected context

The vulnerability occurs in TOTOLINK T6 firmware version 4.1.5cu.748_B20211015

when the static DHCP rule management function is reachable through the

device's web administration interface. Risk is greatest when the relevant

CGI endpoint is exposed to untrusted clients and the function does not

consistently enforce authentication or authorization before changing

configuration.

Exploit preconditions

  • Attack surface: The router's CGI-based web management interface
  • Required access: Network reachability to the affected endpoint; valid

administrative credentials may not be required

  • Trigger point: Processing of requests handled by the

setStaticDhcpRules function

  • Why exploitation is possible: The function permits configuration

changes without applying an adequate access-control check

Why this happens

The underlying bug is an authorization failure in a configuration-management

function. The application accepts a request intended to add or change static

DHCP rules without reliably verifying that the requester has the required

privileges. This behavior maps to CWE-284: Improper Access Control, in

which protected functionality or resources are not sufficiently restricted

to authorized subjects.

Potential impact

  • An attacker may add unauthorized static DHCP assignments
  • An attacker could redirect selected clients to unexpected network

addresses or services

  • Network availability or local traffic behavior may be disrupted
  • Malicious configuration changes can weaken trust in the router's DHCP

environment

  • The device may become a stepping stone for further attacks against local

clients

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every

configuration-changing endpoint, rather than relying on the surrounding

interface or client-side controls.

Common defensive patterns include:

  • Requiring authenticated, authorized sessions for all DHCP rule changes
  • Applying server-side privilege checks before processing or persisting

configuration updates

  • Rejecting requests that do not meet an explicit administrative policy
  • Restricting management interfaces to trusted networks and administrative

paths

  • Preserving least-privilege separation between read-only and

configuration-modifying operations

  • Logging and reviewing changes to DHCP and other network-control settings

How teams detect issues like this

Organizations can look for this weakness through:

  • Static analysis and code review of CGI handlers for missing authorization

checks before state-changing operations

  • Tests that invoke configuration endpoints with unauthenticated and

lower-privilege sessions

  • Web application policy checks requiring authentication and authorization

for all state-changing requests

  • Network monitoring for unexpected requests to DHCP rule management

functions

  • Audit-log review for static DHCP changes that lack a corresponding

authorized administrative action

Automated security review tools may help identify state-changing handlers

that do not enforce consistent access-control policies.

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 from a network position that can reach the

router's affected management endpoint. Exposure depends on network

configuration and whether the management interface is accessible to

untrusted clients.

The reported issue allows unauthenticated attackers to add or change static

DHCP rules, so valid administrative credentials may not be necessary when

the endpoint is reachable.

Enforce server-side authentication and authorization before allowing any

static DHCP rule to be created or modified, and restrict management access

to trusted administrative networks.

Apply consistent access-control middleware to every state-changing endpoint,

test each handler with unauthorized request contexts, and monitor

configuration changes for unexpected activity.

Find out what's already
exploitable in your codebase.