/

CVE-2026-51731

Severity:

CRITICAL RISK

(9.1)

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

CVE-2026-51731

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Unauthorized VLAN Configuration 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 weakness in the TOTOLINK T6 allows unauthenticated attackers to remove VLAN entries through a crafted POST request. The issue becomes risky when the affected management endpoint is reachable and does not adequately verify authorization before processing deletion requests.

Affected context

The vulnerability occurs in the delVlanCfg function of TOTOLINK T6 firmware 4.1.5cu.748_B20211015. Deployments may be exposed when the /cgi-bin/cstecgi.cgi management endpoint is reachable by an attacker and VLAN-management operations are processed without sufficient authentication or authorization checks.

Exploit preconditions

  • Attack surface: The router's HTTP management interface and the /cgi-bin/cstecgi.cgi endpoint
  • Required access: No authentication may be required when the vulnerable request is accepted
  • Trigger point: Processing of a crafted POST request invoking VLAN-entry deletion
  • Why exploitation is possible: The deletion function does not adequately enforce access-control checks before modifying VLAN configuration

Why this happens

The underlying bug is an authorization failure in a state-changing management operation. The delVlanCfg function permits a VLAN deletion request to reach the configuration-modification logic without reliably confirming that the requester is authenticated and authorized. This behavior maps to CWE-284, Improper Access Control, because access restrictions are missing or insufficient for a privileged administrative action.

Potential impact

  • An unauthenticated attacker may remove configured VLAN entries
  • Network segmentation may be disrupted
  • Connected devices could lose expected connectivity or isolation
  • Security controls relying on VLAN separation could be weakened
  • Administrative recovery efforts may be required after configuration changes

General mitigation guidance

Mitigation generally focuses on enforcing authorization consistently for every

state-changing management operation.

Common defensive patterns include:

  • Requiring authentication before exposing administrative configuration actions
  • Applying server-side authorization checks within the deletion function
  • Using deny-by-default access policies for management endpoints
  • Restricting management interfaces to trusted networks or administrative hosts
  • Validating requested VLAN identifiers and requiring explicit confirmation for destructive changes
  • Running management services with only the privileges necessary to alter network configuration
  • Maintaining recoverable configuration backups and monitoring unauthorized changes

How teams detect issues like this

Organizations commonly detect this class of issue through:

  • Static analysis rules identifying state-changing handlers without authentication or authorization checks
  • Code review of management endpoints and functions that delete or modify network configuration
  • Integration tests that verify unauthenticated requests cannot perform administrative actions
  • Web-server and router logs showing unexpected POST requests to configuration endpoints
  • Policy enforcement requiring authorization middleware for all destructive API operations
  • Automated security testing or code-review tools that model access-control paths

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 affected management endpoint is reachable and accepts requests without authentication. Exposure depends on router management-access settings and network placement.

The described weakness allows unauthenticated exploitation, so a valid account may not be required when the vulnerable endpoint is accessible.

Require authentication and enforce authorization inside the VLAN-deletion operation before any configuration change is performed. Restrict administrative interfaces to trusted networks as an additional control.

Apply deny-by-default authorization, test every state-changing endpoint with unauthenticated and unauthorized requests, and monitor logs for unexpected configuration modifications.

Find out what's already
exploitable in your codebase.