/

CVE-2026-51657

Severity:

CRITICAL RISK

(9.1)

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

CVE-2026-51657

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 critical access-control vulnerability in the TOTOLINK T6 allows unauthenticated attackers to retrieve syslog-related configuration through a crafted POST request.

The issue becomes risky when the device exposes the affected CGI endpoint without verifying the caller's authorization, potentially disclosing operational or diagnostic settings.

Affected context

This vulnerability occurs in TOTOLINK T6 devices running version 4.1.5cu.748_B20211015 when the getSyslogCfg function is reachable through the /cgi-bin/cstecgi.cgi interface. Risk depends on whether the endpoint is accessible from an attacker-controlled network and whether the device requires authentication before processing the request.

Exploit preconditions

  • Attack surface: The device's HTTP CGI management interface
  • Required access: Network reachability to the affected endpoint; authentication may not be required
  • Trigger point: A crafted POST request invoking the getSyslogCfg function
  • Why exploitation is possible: The function does not adequately enforce access controls before returning syslog-related configuration

Why this happens

The underlying bug is an authorization failure in which a sensitive configuration retrieval function processes requests without confirming that the requester has the required privileges.

This behavior maps to CWE-284: Improper Access Control. The insecure pattern is exposing a management operation through a request handler while relying on insufficient or missing authentication and authorization checks.

Potential impact

  • An unauthenticated attacker may obtain syslog-related configuration
  • Disclosed settings could reveal device behavior, logging destinations, or operational details
  • Attackers could use the information to improve reconnaissance against the device or network
  • Exposure of configuration data could support follow-on attacks against administrative interfaces or connected services

General mitigation guidance

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

Common defensive patterns include:

  • Requiring authentication and explicit authorization before processing configuration retrieval requests
  • Applying deny-by-default access controls to CGI and management endpoints
  • Limiting management interfaces to trusted administrative networks
  • Avoiding disclosure of sensitive configuration values to lower-privileged users
  • Using least-privilege service identities and separating read access from administrative modification privileges
  • Monitoring and restricting unnecessary external access to router management services

How teams detect issues like this

Organizations can look for this issue through:

  • Static analysis and code review checks for CGI handlers that return configuration without centralized authorization
  • Testing unauthenticated and low-privilege requests against every management endpoint
  • Web server and device-log monitoring for unusual POST requests to CGI interfaces
  • Policy enforcement requiring authentication middleware for administrative APIs
  • Automated security testing that verifies authorization decisions independently for each sensitive operation

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 CGI interface is reachable by an attacker and the affected function accepts requests without authentication.

The key requirement is network access to the affected endpoint. The reported behavior indicates that valid credentials may not be required.

Enforce authentication and authorization before invoking configuration retrieval functions, while limiting management interfaces to trusted networks.

Apply centralized access-control middleware, test each sensitive endpoint with unauthenticated and low-privilege sessions, and monitor administrative interfaces for anomalous requests.

Find out what's already
exploitable in your codebase.