Severity:

HIGH RISK

(7.3)

Improper Access Control in D-Link NAS/Recorder

CVE-2026-4194

Analyzed

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-266, CWE-284

Impact:

Unauthorized Configuration Manipulation and Potential Device Compromise

Severity:

HIGH RISK

(7.3)

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

Multiple D-Link NAS and network recorder models contain an improper access control flaw in the cgi_set_wto function of /cgi-bin/system_mgr.cgi.

When accessed remotely, this endpoint may allow unauthorized manipulation of device settings, enabling attackers to change configuration or behavior without proper permission checks.

Affected context

This vulnerability affects various D-Link DNS and DNR devices (including DNS-120, DNS-320 series, DNS-340L, DNS-343, DNS-345, DNS-726-4, DNS-1100-4, DNS-1200-05, DNS-1550-04, and related DNR models) running firmware up to 20260205.

The issue arises in the web management interface, specifically within /cgi-bin/system_mgr.cgi, where the cgi_set_wto function can be invoked over the network.

In deployments where the management interface is exposed to untrusted networks or lacks additional access controls, the risk of remote abuse increases substantially.

Exploit preconditions

  • Attack surface: HTTP(S) interface of the device, typically on the management port.
  • Required access: Network reachability to the web interface; depending on configuration, this may be from the local network or, in misconfigured setups, from the public internet.
  • Trigger point: Crafted requests sent to /cgi-bin/system_mgr.cgi, targeting the cgi_set_wto functionality.
  • Why exploitation is possible: The handler does not adequately enforce authorization or privilege checks, permitting state-changing operations by users or clients that should not have such rights (CWE-266 / CWE-284).

Why this happens

The root cause is a broken authorization design in the cgi_set_wto function of system_mgr.cgi.

The code path responsible for updating or adjusting system-related parameters trusts incoming requests without reliably verifying that the caller is authenticated and authorized to perform those actions.

This maps to CWE-284: Improper Access Control and CWE-266: Incorrect Privilege Assignment, where privilege boundaries around management operations are not consistently enforced.

As a result, sensitive operations are exposed through a network-accessible endpoint that does not fully respect the intended security policy.

Potential impact

  • Attackers could change device configuration settings without authorization.
  • Malicious modifications may degrade availability or alter recording/storage behavior.
  • Unauthorized changes can weaken other security controls (e.g., access policies, network settings).
  • Compromise of device integrity, potentially contributing to broader network attacks (e.g., pivoting, botnet enrollment).
  • Loss of audit reliability if recording or logging parameters are manipulated.

General mitigation guidance

Effective mitigation focuses on enforcing strong access control around management operations and reducing exposure of administrative interfaces:

  • Ensure that all state-changing CGI handlers perform robust authentication and authorization checks before applying changes.
  • Centralize authorization logic to avoid inconsistencies between different management endpoints.
  • Restrict management interfaces to trusted networks or dedicated management VLANs and avoid exposing them directly to the internet.
  • Apply least-privilege principles so that even authenticated users only receive the minimum capabilities necessary.
  • Introduce defense-in-depth controls such as IP allowlists, reverse proxies, or VPN-only access for administration.
  • Log and monitor configuration changes to detect unusual patterns that might indicate abuse of management functions.

How teams detect issues like this

Detection generally combines code-centric review with behavior monitoring:

  • Perform static analysis or manual review of CGI and web management handlers to locate endpoints that change configuration without explicit authorization checks.
  • Look for direct state modifications in CGI scripts that lack session validation, role checks, or privilege separation.
  • Use web application firewalls or reverse proxies to log and inspect requests to /cgi-bin/system_mgr.cgi, flagging unusual sources, high-frequency changes, or anomalous parameters.
  • Incorporate security testing (e.g., authenticated/unauthenticated fuzzing of management endpoints) into QA and CI/CD pipelines.
  • Leverage automated code review tools to enforce policies requiring access control checks on all management and configuration functions.

Sources

SourceLink
github.comgithub.com/wudipjq/my_vuln/blob/main/D-Link8/vuln_96/96.md
vuldb.comvuldb.com/?ctiid.351106
vuldb.comvuldb.com/?id.351106
vuldb.comvuldb.com/?submit.769853
dlink.comdlink.com/

Frequently asked

questions

Yes. If the device's management interface is reachable over the network (for example, from a local LAN or the internet), an attacker can potentially exploit this issue remotely by sending crafted requests to the vulnerable CGI endpoint.

The attacker typically needs only network-level access to the management interface. In some configurations, no valid credentials are required if the access control checks are missing or improperly enforced on the affected function.

The safest approach is to enforce strict, centralized authorization for all configuration-changing operations and ensure that each management endpoint validates both authentication and role-based permissions before applying any changes.

Adopt a consistent access control framework for all management APIs, perform regular security code reviews of administrative endpoints, limit exposure of management interfaces, and enforce policies (automated where possible) that require explicit authorization checks for every privileged action.

Find out what's already
exploitable in your codebase.