/

CVE-2026-51623

Severity:

HIGH RISK

(7.5)

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

CVE-2026-51623

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 DDNS status function allows unauthenticated users to retrieve runtime DDNS information and the device's public IP address.

The issue becomes risky when the affected endpoint is reachable over a network and does not require a valid authenticated session before returning status data.

Affected context

The vulnerability occurs in the TOTOLINK T6 4.1.5cu.748_B20211015 firmware, within the getDdnsStatus function exposed through /cgi-bin/cstecgi.cgi. Deployments may be affected when the DDNS status operation is accessible without authentication and the device exposes the management interface to an untrusted network.

Exploit preconditions

  • Attack surface: The router's web management interface and its CGI request handler
  • Required access: Network reachability to the affected endpoint; valid authentication may not be required
  • Trigger point: A crafted POST request targeting the DDNS status operation
  • Why exploitation is possible: The function does not correctly enforce authorization before disclosing runtime DDNS and public IP information

Why this happens

The underlying defect is an authorization failure in a sensitive management operation. The getDdnsStatus function processes a request and returns device information without reliably verifying that the caller has the required privileges. This maps to CWE-284: Improper Access Control, where access restrictions are missing, incomplete, or incorrectly applied to protected functionality and data.

Potential impact

  • Unauthenticated users may obtain DDNS runtime status
  • An attacker could learn the router's public IP address
  • Disclosed network information may support reconnaissance against the device or connected services
  • The exposure could contribute to broader attacks when combined with other router vulnerabilities

General mitigation guidance

Mitigation generally centers on enforcing authorization consistently at the endpoint and function boundaries.

Common defensive patterns include:

  • Require a valid authenticated session and appropriate privilege before processing DDNS status requests
  • Apply deny-by-default access controls to administrative CGI operations
  • Avoid exposing management interfaces to untrusted networks where feasible
  • Return only the minimum status information necessary for the requesting user
  • Use centralized authorization checks so individual functions cannot bypass policy
  • Separate router administration from general network access through segmentation and least privilege

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis and code review checks for sensitive handlers that lack authentication or authorization calls
  • Tests that invoke management endpoints with no session, expired sessions, and insufficient privileges
  • Web-server and router logs showing unauthenticated POST requests to CGI operations
  • API authorization policies requiring explicit access control for every administrative function
  • Automated security testing that compares responses between authenticated and unauthenticated requests

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 reachable when the router's management interface is exposed to the attacker's network. Exploitability depends on network placement and administrative-interface exposure.

The reported behavior indicates that authentication is not required to obtain the DDNS runtime status and public IP information.

Require authentication and enforce an appropriate authorization decision before the DDNS status function processes a request or returns data.

Apply deny-by-default policies to management endpoints, test unauthenticated and low-privilege access paths, minimize returned information, and monitor requests to administrative CGI interfaces.

Find out what's already
exploitable in your codebase.