CVE-2025-10964:

Command injection vulnerability in Wavlink NU516U1 firewall.cgi allows remote attackers to execute arbitrary commands.

Score
A numerical rating that indicates how dangerous this vulnerability is.

8.8High

Published Date:Sep 25, 2025
CISA KEV Date:*No Data*
Industries Affected:20

Threat Predictions

EPSS Score:0.4
EPSS Percentile:62%

Exploitability

Score:2.8
Attack Vector:NETWORK
Attack Complexity:LOW
Privileges Required:LOW
User Interaction:NONE
Scope:UNCHANGED

Impact

Score:5.9
Confidentiality Impact:HIGH
Integrity Impact:HIGH
Availability Impact:HIGH

Description Preview

Command injection vulnerability in Wavlink NU516U1 firewall.cgi allows remote attackers to execute arbitrary commands.

Overview

The vulnerability in Wavlink NU516U1 is classified as a command injection flaw, identified by CVE-2025-10964. It affects the firewall configuration interface and can be exploited remotely with low attack complexity. The CVSS v3.1 base score is 6.3, indicating medium severity. The attack vector is network-based, requires no user interaction, and can be initiated with low privileges. This vulnerability allows an attacker to execute arbitrary commands on the affected system, potentially leading to unauthorized access, data manipulation, or service disruption. The public availability of an exploit increases the likelihood of attacks against unpatched systems.

Remediation

As of the vulnerability disclosure, no official patch or mitigation strategy has been provided by the vendor. The lack of vendor response to the initial disclosure suggests that a fix may not be immediately forthcoming. In the absence of an official patch, network administrators should implement the following temporary measures:
1. Restrict access to the device's management interface to trusted IP addresses only.
2. Implement strong network segmentation to isolate affected devices.
3. Monitor logs for suspicious activities related to the firewall.cgi file.
4. Consider disabling remote management features if not strictly necessary.
5. Regularly check for and apply any firmware updates that may address this vulnerability.
6. Consider replacing the affected device with a more secure alternative if possible.
It is crucial to maintain vigilance and monitor for any vendor communications regarding a permanent fix for this vulnerability.