/

CVE-2026-51674

Severity:

CRITICAL RISK

(9.8)

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

CVE-2026-51674

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Unauthorized Configuration and Denial of Service

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

An improper access control vulnerability in the TOTOLINK T6 allows unauthenticated attackers to configure forced reboot tasks through a crafted request to the device's CGI endpoint. Successful abuse could repeatedly disrupt router availability without requiring valid credentials.

Affected context

The issue occurs in the TOTOLINK T6 4.1.5cu.748_B20211015 firmware when the setScheduleCfg function processes requests to /cgi-bin/cstecgi.cgi. Risk is greatest when the management interface or affected endpoint is reachable by an attacker and the function does not enforce authentication or authorization before accepting reboot scheduling changes.

Exploit preconditions

  • Attack surface: The router's CGI-based management endpoint
  • Required access: Network access to the affected endpoint; valid credentials may not be required
  • Trigger point: Processing of a crafted POST request by setScheduleCfg
  • Why exploitation is possible: The function permits configuration changes without adequately verifying the requester's authorization

Why this happens

The vulnerability results from missing or ineffective authorization checks in a configuration-changing function. The endpoint accepts a request that can alter scheduled reboot behavior without confirming that the caller has the required administrative privileges. This maps to CWE-284: Improper Access Control, where access to a protected operation is not sufficiently restricted.

Potential impact

  • An attacker may configure repeated or timed forced reboots
  • Router availability could be disrupted
  • Network connectivity for dependent users and services may be interrupted
  • Administrative control over device scheduling settings could be altered without authorization

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every configuration-changing endpoint and reducing exposure of administrative interfaces.

Common defensive patterns include:

  • Require authenticated and appropriately privileged sessions before processing configuration changes
  • Apply centralized authorization checks consistently across CGI handlers
  • Validate requested schedule values and reject unexpected or excessive configurations
  • Restrict management interfaces to trusted networks or administrative channels
  • Use least-privilege administrative roles and separate read-only operations from changes
  • Monitor and protect configuration endpoints with network access controls and request policies

How teams detect issues like this

Organizations can assess for this class of issue through:

  • Static analysis for state-changing handlers that lack authentication or authorization checks
  • Code review of CGI endpoints and functions that modify device configuration
  • Dynamic testing that verifies unauthenticated requests cannot alter reboot schedules
  • API and network policy checks requiring authorization for administrative operations
  • Logging and alerting for unexpected schedule changes or repeated forced reboots
  • Automated security testing tools that review access-control behavior across management endpoints

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 exploitable over the network when the affected CGI endpoint is reachable. Exposure depends on router management-interface configuration and network controls.

The described issue allows unauthenticated attackers to submit the relevant request, so valid administrative credentials may not be required.

Enforce authentication and authorization before allowing any request to change reboot scheduling or other device configuration.

Apply centralized access-control checks to every state-changing endpoint, limit management exposure, validate configuration values, and test administrative APIs for unauthenticated modification paths.

Find out what's already
exploitable in your codebase.