/

CVE-2026-51695

Severity:

HIGH RISK

(7.5)

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

CVE-2026-51695

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Unauthorized Dynamic DNS 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

TOTOLINK T6 contains an access-control flaw in the setDdnsCfg function that can allow unauthenticated attackers to change dynamic DNS settings. The issue becomes risky when the CGI endpoint accepts crafted POST requests without adequately verifying the caller's authorization.

Affected context

The vulnerability occurs in TOTOLINK T6 firmware 4.1.5cu.748_B20211015, within the setDdnsCfg function exposed through /cgi-bin/cstecgi.cgi. Risk depends on the endpoint being reachable by an attacker and on the device failing to enforce authentication or authorization before processing dynamic DNS configuration changes.

Exploit preconditions

  • Attack surface: The router's CGI web interface and its /cgi-bin/cstecgi.cgi endpoint
  • Required access: Network reachability to the endpoint; valid authentication may not be required
  • Trigger point: A crafted POST request targeting the dynamic DNS configuration handler
  • Why exploitation is possible: The function does not adequately restrict access before accepting and applying configuration changes

Why this happens

The underlying bug is an authorization failure in a configuration-changing handler. The setDdnsCfg function processes requests that can alter dynamic DNS state without reliably establishing that the requester is permitted to perform the operation. This behavior maps to CWE-284: Improper Access Control, where a protected resource or administrative action is insufficiently restricted.

Potential impact

  • An attacker could alter the device's dynamic DNS state
  • Traffic or remote administration workflows could be redirected to attacker-controlled infrastructure
  • The device's availability or remote reachability could be disrupted
  • Network users could be exposed to phishing, interception, or other follow-on attacks
  • Compromise of DNS-related configuration could support broader router abuse

General mitigation guidance

Mitigation generally focuses on enforcing authorization consistently for every configuration-changing operation.

Common defensive patterns include:

  • Requiring authenticated sessions and explicit authorization before processing dynamic DNS changes
  • Applying server-side access checks rather than relying on client-side controls or request structure
  • Validating configuration values against strict allowlists and expected formats
  • Limiting administrative interfaces to trusted network segments where practical
  • Running management services with least privilege and isolating them from public-facing interfaces
  • Recording and alerting on unexpected changes to dynamic DNS settings

How teams detect issues like this

Organizations can assess for this class of issue through:

  • Static analysis of CGI handlers for configuration writes that lack centralized authorization checks
  • Code review searches for administrative endpoints that process POST data before session validation
  • Dynamic testing that compares endpoint behavior for authenticated and unauthenticated requests
  • API and router policy checks requiring authentication for all state-changing operations
  • Monitoring for unexpected dynamic DNS changes, unusual management requests, and configuration updates from untrusted networks

Automated security testing tools may help identify exposed state-changing endpoints, but authorization requirements should also be verified through targeted review.

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 remotely when the router's CGI interface is network-reachable and the affected endpoint accepts unauthenticated requests. Exposure depends on deployment and management-interface access controls.

The described issue permits unauthenticated access to the affected operation, so a valid account may not be required when the endpoint is reachable.

Require authentication and enforce server-side authorization before any dynamic DNS configuration is read or changed. Validate submitted values and restrict management access to trusted networks.

Apply centralized authorization middleware to all state-changing handlers, test unauthenticated and low-privilege access paths, and monitor administrative configuration changes.

Find out what's already
exploitable in your codebase.