/

CVE-2026-51643

Severity:

CRITICAL RISK

(9.1)

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

CVE-2026-51643

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Unauthorized Information Disclosure

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 broken access control vulnerability in the TOTOLINK T6 allows unauthenticated clients to request NTP configuration and current time data through a crafted POST request. The issue becomes risky when the device exposes the affected CGI endpoint without requiring authentication or enforcing authorization checks.

Affected context

The vulnerability occurs in the getNtpCfg function of TOTOLINK T6 firmware 4.1.5cu.748_B20211015, where the /cgi-bin/cstecgi.cgi interface may process NTP-configuration requests without confirming that the requester is authorized. Deployments in which the management interface is reachable by untrusted networks may have greater exposure.

Exploit preconditions

  • Attack surface: The device's HTTP CGI management interface
  • Required access: Network connectivity to the affected endpoint; authentication may not be required
  • Trigger point: A crafted POST request that invokes the getNtpCfg function
  • Why exploitation is possible: The function may return protected configuration and time data without an effective authorization check

Why this happens

The underlying bug is an authorization failure in a management interface. The getNtpCfg function appears to trust a request before verifying whether the caller has permission to access NTP settings. This behavior maps to CWE-284, Improper Access Control, because a protected operation does not consistently enforce the intended access policy.

Potential impact

  • An attacker may obtain NTP server and synchronization configuration
  • An attacker could learn current device time data useful for reconnaissance
  • Exposed configuration may aid further attacks against the device or network
  • Repeated unauthenticated access can weaken confidence in management-interface isolation

General mitigation guidance

Mitigation generally focuses on enforcing authentication and authorization at the CGI routing and function levels, rather than relying on client behavior or obscurity. Sensitive configuration responses can be minimized, and unauthenticated requests can receive a uniform denial response. Management interfaces are commonly isolated from untrusted networks, protected by network-level policy, and operated with least privilege. Secure-by-default designs should require explicit authorization for every configuration-read operation and should reduce the amount of information returned to callers.

How teams detect issues like this

  • Review CGI handlers and dispatch logic for configuration functions that lack centralized authorization checks
  • Use static analysis or secure code review rules to identify sensitive operations reachable before authentication
  • Test management endpoints with unauthenticated requests and verify that protected data is denied
  • Monitor access logs for repeated POST requests to CGI endpoints and unusual requests for configuration functions
  • Enforce network policies that limit management-interface exposure to trusted administration paths

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 remotely exploitable when the device's management interface and affected CGI endpoint are reachable by an attacker. Exposure depends on network placement and access-control configuration.

The described issue permits unauthenticated access, so valid credentials may not be required when the endpoint is reachable and the vulnerable behavior is present.

Require authentication and an explicit authorization decision before processing NTP-configuration requests, and return only the minimum necessary data.

Apply centralized access-control middleware to management endpoints, test every sensitive operation without credentials, and restrict administrative interfaces to trusted networks.

Find out what's already
exploitable in your codebase.