/

CVE-2026-51673

Severity:

HIGH RISK

(7.5)

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

CVE-2026-51673

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Unauthorized configuration modification

Severity:

HIGH RISK

(7.5)

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 high-severity access control weakness in the TOTOLINK T6 allows requests to the setNtpCfg function without adequate authentication or authorization. An unauthenticated attacker may change the router's time synchronization settings by sending a specially crafted POST request to the CGI endpoint.

Affected context

The vulnerability occurs in TOTOLINK T6 firmware version 4.1.5cu.748_B20211015 when the web management interface exposes the cstecgi.cgi endpoint and the setNtpCfg function does not sufficiently enforce access controls. The risk is greater when the management interface is reachable from an untrusted network.

Exploit preconditions

  • Attack surface: The router's CGI-based web management interface - Required access: Network connectivity to the affected endpoint; authentication

may not be required

  • Trigger point: A POST request processed by the setNtpCfg function - Why exploitation is possible: The function accepts configuration changes

without adequately verifying the requester's authorization

Why this happens

The underlying bug is an authorization failure in a management function. The setNtpCfg handler processes a request that changes security-relevant device configuration without consistently enforcing authentication and authorization checks. This maps to CWE-284, which covers improper access control over protected resources or operations.

Potential impact

  • An attacker may alter the router's time synchronization configuration.
  • System logs and time-dependent security records could become less reliable.
  • Scheduled or certificate-dependent behavior could be disrupted.
  • The device's configuration integrity could be weakened.
  • The change could support follow-on attacks that rely on misleading timestamps.

General mitigation guidance

Mitigation generally focuses on enforcing authentication and authorization for every configuration-changing management operation. Sensitive CGI handlers should use secure-by-default access controls, reject unauthenticated state changes, and validate both the requested fields and the caller's privilege level. Management interfaces are best limited to trusted administration networks, with unnecessary external exposure reduced. Administrative roles should follow least-privilege principles, and configuration changes should be auditable and protected against unauthorized modification.

How teams detect issues like this

Detection can include static analysis and code review for CGI handlers that modify configuration without a centralized authorization check, inconsistent authentication guards, or direct use of request parameters in privileged functions. Dynamic testing can verify that unauthenticated and low-privilege requests are denied for every state-changing endpoint. Web and device logs can be monitored for unexpected POST requests to cstecgi.cgi, unexplained NTP configuration changes, and management access from untrusted networks. Automated review tools and policy checks can flag exposed administrative endpoints and missing authorization enforcement.

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 router's management interface

and affected CGI endpoint are reachable by an attacker. The exact scope

depends on deployment and network exposure.

The described weakness allows unauthenticated requests to alter the affected

settings, although network access to the endpoint is still required.

Require authentication and explicit authorization before processing every

configuration-changing request, and apply least-privilege checks to the

administrative operation.

Centralize access-control enforcement, test anonymous and low-privilege access

paths, restrict management interfaces to trusted networks, and audit

configuration changes.

Find out what's already
exploitable in your codebase.