/

CVE-2026-51615

Severity:

HIGH RISK

(7.5)

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

CVE-2026-51615

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Unauthorized Information Disclosure

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

An incorrect access control check in the TOTOLINK T6 router's getLanCfg function may expose LAN addressing and DHCP configuration details.

An unauthenticated attacker could retrieve this information by sending a specially crafted POST request to the router's CGI endpoint, if the management interface is reachable.

Affected context

The vulnerability occurs in TOTOLINK T6 devices using the affected router software and exposing the /cgi-bin/cstecgi.cgi endpoint. Risk is increased when the management interface is accessible to untrusted networks and the getLanCfg function does not require appropriate authentication or authorization before returning LAN and DHCP configuration data.

Exploit preconditions

  • Attack surface: The router's CGI management endpoint
  • Required access: Network connectivity to the exposed management interface; authentication may not be required
  • Trigger point: A crafted POST request targeting the getLanCfg function
  • Why exploitation is possible: The function fails to enforce sufficient access control before disclosing LAN addressing and DHCP configuration information

Why this happens

The underlying bug is an authorization failure in a management API. The getLanCfg function exposes configuration data without reliably verifying that the requester is authenticated and permitted to access it.

This behavior maps to CWE-284: Improper Access Control, where a security-sensitive resource or operation is not adequately restricted to authorized users. The insecure pattern is treating an externally supplied request as trusted before applying endpoint- and data-level authorization checks.

Potential impact

  • An attacker may learn internal LAN addressing information
  • An attacker could obtain DHCP configuration details useful for network reconnaissance
  • The disclosed information may support follow-on attacks against local devices or services
  • Network topology and configuration exposure can reduce the effectiveness of defensive segmentation

General mitigation guidance

Mitigation generally focuses on enforcing authentication and authorization consistently across all router management functions.

Common defensive patterns include:

  • Requiring authenticated, authorized sessions for configuration-disclosure endpoints
  • Applying authorization checks before processing requests or returning sensitive fields
  • Limiting management interfaces to trusted administrative networks
  • Returning only the minimum configuration data required for an authorized operation
  • Using secure-by-default management exposure and network isolation
  • Running management services with narrowly scoped privileges and clear policy enforcement

These controls reduce exposure even when an endpoint receives unexpected or crafted requests.

How teams detect issues like this

Organizations can look for this weakness through:

  • Static and API security analysis that identifies management handlers lacking authorization checks
  • Code review signals such as direct configuration disclosure from CGI functions
  • Tests that call administrative endpoints with no credentials and with insufficient roles
  • Web-server and router logs showing repeated POST requests to configuration functions
  • Network policies that alert on management-interface access from untrusted segments
  • Automated security review tools that check endpoint authentication and authorization coverage

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 CGI endpoint is reachable by an attacker. Exposure depends on interface configuration, network segmentation, and deployment context.

The described issue allows unauthenticated access, so valid credentials may not be required when the affected endpoint is exposed.

Require authentication and enforce endpoint- and data-level authorization before allowing access to LAN or DHCP configuration information.

Use deny-by-default management interfaces, test every administrative endpoint without credentials and with low-privilege accounts, minimize returned data, and monitor access from untrusted networks.

Find out what's already
exploitable in your codebase.