/

CVE-2026-51733

Severity:

CRITICAL RISK

(9.8)

Broken Access Control (CWE-284) in TOTOLINK T6 CGI

CVE-2026-51733

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Unauthorized Configuration Modification

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 FirmwareUpgrade function allows unauthenticated attackers to remove Wi-Fi schedule entries through a crafted request.

The issue becomes risky when the management CGI endpoint is reachable and fails to verify authorization before processing schedule-related actions.

Affected context

This vulnerability occurs in TOTOLINK T6 firmware version 4.1.5cu.748_B20211015, within the FirmwareUpgrade function exposed through /cgi-bin/cstecgi.cgi. Deployments may be affected when this endpoint is accessible to an attacker and the function processes requests without confirming that the requester is authenticated and authorized to change Wi-Fi schedule entries.

Exploit preconditions

  • Attack surface: The router's CGI management interface
  • Required access: Network reachability to the affected endpoint; authentication may not be required
  • Trigger point: A crafted POST request handled by the FirmwareUpgrade function
  • Why exploitation is possible: The function does not adequately enforce authorization before allowing Wi-Fi schedule entries to be removed

Why this happens

The underlying flaw is improper enforcement of authorization checks around a state-changing administrative operation. The FirmwareUpgrade function accepts a request that can alter router configuration without reliably establishing that the caller has the required privileges. This behavior maps to CWE-284: Improper Access Control, in which access restrictions are missing, incorrectly applied, or bypassable.

Potential impact

  • Unauthorized removal of Wi-Fi schedule entries
  • Disruption of scheduled network access policies
  • Loss of intended parental-control or availability restrictions
  • Configuration integrity degradation
  • Broader router compromise if related unauthenticated administrative operations are exposed

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every state-changing management operation and reducing exposure of administrative interfaces.

Common defensive patterns include:

  • Requiring authentication and explicit authorization before processing configuration changes
  • Applying deny-by-default access policies to management CGI endpoints
  • Validating request context, operation scope, and target configuration object server-side
  • Restricting administrative interfaces to trusted networks or management paths
  • Running management functions with only the privileges needed for the requested operation
  • Preserving audit records for configuration changes and rejecting ambiguous request formats

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 of CGI routes, firmware-management functions, and configuration mutation logic
  • Tests that submit administrative requests with missing, expired, or insufficient credentials
  • Web and device logs showing unauthenticated POST requests to management endpoints
  • Policy enforcement requiring authorization middleware for all configuration-changing routes
  • Automated security review tools that flag publicly reachable administrative operations without access-control gates

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

Yes, it may be exploitable over the network when the affected CGI endpoint is reachable. The precise scope depends on the router's network exposure and management-interface configuration.

The described issue permits unauthenticated access to the affected operation, so a valid account may not be required when the endpoint is exposed.

Require authentication and enforce an explicit authorization decision before allowing any Wi-Fi schedule or other configuration change.

Apply centralized access-control checks to all administrative routes, test unauthenticated and low-privilege requests, restrict management interfaces to trusted networks, and monitor configuration changes.

Find out what's already
exploitable in your codebase.