CVE-2025-11096
BaseFortify
Publication date: 2025-09-28
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| dlink | dir-823x_firmware | 250416 |
| dlink | dir-823x | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-77 | The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-11096 is a command injection vulnerability in the D-Link DIR-823X router (version 250416). It occurs in the /goform/diag_traceroute endpoint where the 'target_addr' parameter is not properly sanitized. This flaw allows a remote attacker to inject and execute arbitrary commands on the device without authentication, potentially compromising the router's security. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing remote attackers to execute arbitrary commands on your D-Link DIR-823X router, which can compromise the confidentiality, integrity, and availability of the device. Attackers could take control of the router, disrupt network services, or use the device as a foothold for further attacks. Since exploitation requires no authentication and is easy to perform, it poses a significant security risk. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection can be performed by monitoring or testing the /goform/diag_traceroute endpoint for command injection attempts via the target_addr parameter. For example, sending crafted HTTP requests to the router's /goform/diag_traceroute endpoint with payloads in the target_addr parameter that include command injection patterns (e.g., semicolons, backticks) can help identify if the device is vulnerable. A sample curl command to test might be: curl -v --data "target_addr=8.8.8.8;id" http://<router-ip>/goform/diag_traceroute. Network intrusion detection systems (NIDS) can also be configured to alert on suspicious requests to this endpoint containing unusual characters or command injection patterns. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the affected router's management interface from untrusted networks, such as disabling remote administration or limiting it to trusted IP addresses. Since no known countermeasures or patches are currently available, replacing the affected device with a secure model is recommended. Additionally, monitoring network traffic for exploitation attempts and applying network-level protections like firewalls or intrusion prevention systems to block malicious requests targeting /goform/diag_traceroute can help reduce risk. [1]