/

CVE-2026-51716

Severity:

HIGH RISK

(7.5)

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

CVE-2026-51716

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Unauthorized modification of network configuration and potential service disruption

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 delPortForwardRules function that permits unauthenticated attackers to delete port-forwarding rules. The issue becomes risky when the router exposes the affected CGI endpoint and does not require authorization before processing deletion requests.

Affected context

The vulnerability occurs in TOTOLINK T6 4.1.5cu.748_B20211015 deployments where the web management interface exposes the /cgi-bin/cstecgi.cgi endpoint and the delPortForwardRules operation does not adequately enforce access checks. Risk depends on network exposure and whether requests to the endpoint can reach the device without an authenticated session.

Exploit preconditions

  • Attack surface: The router's HTTP management CGI endpoint - Required access: Network reachability to the affected endpoint; valid

authentication may not be required

  • Trigger point: Processing of a crafted POST request invoking the

delPortForwardRules function

  • Why exploitation is possible: The deletion operation can be reached without

sufficient authorization enforcement

Why this happens

The underlying bug is an authorization failure in a state-changing management operation. The delPortForwardRules function processes requests that modify port-forwarding configuration without reliably verifying that the requester has permission to perform the operation. This behavior maps to CWE-284, Improper Access Control, because access restrictions are missing or ineffective for a protected administrative function.

Potential impact

  • An attacker may delete configured port-forwarding rules.
  • Internal services that rely on those rules could become unreachable from

expected external networks.

  • Network availability or remote-access workflows could be disrupted.
  • Repeated unauthorized changes could complicate administration and incident

response.

General mitigation guidance

Mitigation generally focuses on enforcing authorization at the server-side handler for every configuration-changing operation. Secure-by-default designs should deny access unless an authenticated and authorized administrative context is established, rather than relying on client-side controls or endpoint obscurity. Management interfaces can be kept on trusted networks, configuration changes can be limited to least-privileged roles, and request validation can reduce trust in client-supplied operation names and parameters. Additional protections may include session integrity checks, audit logging, and policy enforcement for administrative API access.

How teams detect issues like this

Detection approaches include static analysis and code review for management handlers that change device state without centralized authorization checks. Reviewers can look for CGI dispatch paths that invoke administrative functions based only on request parameters, inconsistent authentication checks, and missing role validation. Network monitoring and device audit logs can identify unauthenticated or unexpected POST requests to management endpoints and sudden deletion of port-forwarding rules. Automated security review tools may help flag exposed state-changing endpoints and missing access-control enforcement.

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 affected management endpoint is

reachable and the request is accepted without authentication. Exposure

depends on router configuration, network placement, and management-interface

access controls.

The described flaw allows unauthenticated access to the deletion operation, so

a valid account may not be required when the endpoint is reachable.

Enforce server-side authentication and authorization for the

delPortForwardRules operation and all other state-changing management

functions, using a default-deny policy.

Centralize access-control checks, restrict management interfaces to trusted

networks, apply least privilege, validate administrative requests, and

monitor configuration changes through reliable audit logging.

Find out what's already
exploitable in your codebase.