/

CVE-2026-51687

Severity:

CRITICAL RISK

(9.1)

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

CVE-2026-51687

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Unauthorized Wireless Access Configuration

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 vulnerability in the TOTOLINK T6 allows unauthenticated attackers to create or weaken guest wireless access through a crafted HTTP POST request.

The issue becomes risky when the device exposes the affected configuration endpoint and does not require authorization before applying guest-network changes.

Affected context

The vulnerability occurs in the setWiFiEasyGuestCf function of TOTOLINK T6 firmware version 4.1.5cu.748_B20211015. It affects deployments where the router accepts requests to /cgi-bin/cstecgi.cgi without adequately verifying the caller's authorization before changing guest wireless settings.

Exploit preconditions

  • Attack surface: The router's HTTP configuration interface and associated CGI endpoint
  • Required access: No authentication may be required when the vulnerable request is accepted
  • Trigger point: A crafted POST request targeting the guest Wi-Fi configuration operation
  • Why exploitation is possible: The function does not sufficiently enforce authorization before allowing guest wireless settings to be created or weakened

Why this happens

The underlying bug is an authorization failure in a sensitive configuration operation. The affected function performs or permits guest-network changes without reliably checking whether the requester has the required privileges, mapping to CWE-284: Improper Access Control. This reflects an insecure pattern in which an administrative action is reachable through an endpoint that lacks effective authentication or authorization enforcement.

Potential impact

  • Unauthorized creation or modification of guest wireless access
  • Weakened wireless access restrictions
  • Unauthorized network connectivity for nearby or remote users, depending on exposure
  • Increased risk of access to internal services reachable from the guest network
  • Loss of control over router security policy

General mitigation guidance

Mitigation generally focuses on enforcing authorization at the point where sensitive wireless configuration changes are processed.

Common defensive patterns include:

  • Requiring strong authentication and explicit authorization for every administrative configuration action
  • Applying deny-by-default access controls to router management endpoints
  • Separating guest-network configuration privileges from general request handling
  • Validating session state, privilege level, and request origin before applying changes
  • Restricting management interfaces to trusted networks and disabling unnecessary external exposure
  • Running configuration services with the minimum privileges needed to perform their tasks

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis and code review checks for administrative handlers that modify configuration without centralized authorization checks
  • Testing unauthenticated and low-privilege requests against CGI endpoints that alter wireless settings
  • Monitoring router logs for guest-network configuration changes without corresponding authenticated administrator activity
  • Policy enforcement requiring authentication and authorization middleware for all configuration-management routes
  • Automated security testing that compares behavior across authenticated, unauthenticated, and differently privileged sessions

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

Exploitability depends on how the router's management interface is exposed. It may be reachable over the local network, and broader exposure could increase the attack surface.

The described flaw permits unauthenticated attackers to submit the affected request, so a valid administrative account may not be required.

Require authentication and enforce authorization at the server-side handler before accepting any guest wireless configuration change.

Apply centralized access-control checks to every management endpoint, use deny-by-default policies, limit management exposure, and test sensitive operations with multiple privilege levels.

Find out what's already
exploitable in your codebase.