/

CVE-2026-51736

Severity:

CRITICAL RISK

(9.1)

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

CVE-2026-51736

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Unauthorized Log Deletion

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 erase system logs through a crafted POST request to the device's CGI interface. The issue becomes risky when the affected management endpoint is reachable and fails to require authorization before invoking the log-clearing function.

Affected context

The vulnerability occurs in the clearSyslog function of TOTOLINK T6 firmware when the web management interface exposes /cgi-bin/cstecgi.cgi and the function does not enforce authentication or authorization. Deployments that restrict management access and isolate administration interfaces may reduce exposure, but the endpoint's access-control behavior remains the relevant risk condition.

Exploit preconditions

  • Attack surface: The router's HTTP or HTTPS CGI management interface
  • Required access: Network connectivity to the affected management endpoint; valid credentials may not be required
  • Trigger point: A crafted POST request targeting the clearSyslog function
  • Why exploitation is possible: The function performs a security-sensitive log-deletion operation without adequately verifying the requester's authorization

Why this happens

The underlying bug is an authorization failure in a security-sensitive administrative function. The application permits a request to reach clearSyslog without first enforcing an appropriate authentication and authorization decision, matching CWE-284: Improper Access Control. Insecure endpoint design, missing privilege checks, or reliance on client-side controls can allow unauthenticated callers to invoke operations intended only for administrators.

Potential impact

  • Attackers may erase system logs without authorization
  • Security teams could lose forensic evidence needed to investigate incidents
  • Audit trails may become incomplete or misleading
  • Malicious activity could be concealed for longer
  • Monitoring and accountability controls could be weakened

General mitigation guidance

Mitigation generally focuses on protecting administrative operations with server-side access-control decisions.

Common defensive patterns include:

  • Requiring authentication and explicit administrative authorization before log deletion
  • Applying deny-by-default controls to management CGI functions
  • Enforcing authorization checks consistently on every request path, including direct endpoint access
  • Restricting management interfaces to trusted networks or administrative channels
  • Preserving logs through centralized, append-only logging that the device cannot independently erase
  • Running management functions with only the privileges required for their intended operation
  • Avoiding reliance on hidden endpoints, client-side checks, or obscurity as security controls

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis and endpoint reviews that identify sensitive functions without server-side authorization checks
  • Code review signals such as direct dispatch from CGI parameters to administrative operations
  • Tests that invoke management endpoints without credentials and verify that access is denied
  • Network monitoring for unauthenticated POST requests to administrative CGI paths
  • Policy enforcement requiring authentication, authorization, and audit logging for destructive management actions
  • Automated security testing or code-review tools that flag missing access-control checks

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 network reachability. An attacker who can access the exposed management interface may be able to invoke the log-clearing function without authentication.

The described issue indicates that authentication is not required for the affected operation, although network access to the endpoint is still necessary.

Require server-side authentication and explicit authorization before allowing any request to delete or alter system logs.

Apply deny-by-default access control to administrative endpoints, test unauthenticated and low-privilege requests, restrict management interfaces, and use centralized tamper-resistant logging.

Find out what's already
exploitable in your codebase.