CVE-2026-3612
Command Injection in Wavlink OTA Upgrade Allows Remote Exploits
Publication date: 2026-03-06
Last updated on: 2026-03-10
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wavlink | wl-nu516u1_firmware | m16u1_v240425 |
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?
[{'type': 'paragraph', 'content': 'CVE-2026-3612 is a critical command injection vulnerability in the Wavlink WL-NU516U1 router firmware version V240425. It exists in the OTA Online Upgrade component, specifically in the sub_405AF4 function of the /cgi-bin/adm.cgi file. The vulnerability arises from unsafe handling of the firmware_url parameter, which is directly concatenated into a system command without proper sanitization.'}, {'type': 'paragraph', 'content': 'Although the firmware_url parameter is enclosed in double quotes to prevent argument escaping, this does not prevent shell command substitution techniques such as $() or backticks. An authenticated remote attacker can exploit this flaw by injecting malicious shell commands through the firmware_url parameter, resulting in arbitrary command execution with root privileges on the device.'}, {'type': 'paragraph', 'content': 'Exploitation requires authentication, typically using the default administrative password "admin". The vulnerability allows attackers to execute arbitrary system commands remotely, leading to full device compromise.'}] [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including complete compromise of the affected device. An attacker who successfully exploits this flaw can execute arbitrary commands with root privileges remotely.
- Full control over the device, including the ability to modify, delete, or steal data.
- Disruption of device availability by executing commands that could crash or disable the device.
- Potential pivot point for further attacks within a network due to the elevated privileges gained.
Since the exploit is publicly available and easy to execute, the risk of compromise is high, especially if default credentials are used or authentication is weak.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'Detection of this vulnerability involves checking for exploitation attempts targeting the /cgi-bin/adm.cgi endpoint, specifically POST requests with the page parameter set to ota_new_upgrade and a crafted firmware_url parameter containing shell command substitution patterns such as $() or backticks.'}, {'type': 'paragraph', 'content': 'A proof-of-concept involves sending a POST request to /cgi-bin/adm.cgi with the firmware_url parameter containing malicious shell commands, for example, $(touch /tmp/pwned). Detection can be done by monitoring for unexpected files like /tmp/pwned or unusual command execution traces on the device.'}, {'type': 'paragraph', 'content': 'Since exploitation requires authentication, monitoring for unusual authenticated sessions or unexpected POST requests to the OTA upgrade functionality can help detect attempts.'}, {'type': 'list_item', 'content': 'Use network monitoring tools to capture POST requests to /cgi-bin/adm.cgi with page=ota_new_upgrade.'}, {'type': 'list_item', 'content': 'Inspect logs for firmware_url parameters containing shell command substitution characters such as `$()`, backticks (`), or other suspicious shell metacharacters.'}, {'type': 'list_item', 'content': 'On the device, check for unexpected files created by exploits, e.g., /tmp/pwned.'}, {'type': 'list_item', 'content': "Example command to detect suspicious POST requests (using tcpdump and grep): `tcpdump -A -s 0 'tcp port 80' | grep -i 'ota_new_upgrade'`"}, {'type': 'list_item', 'content': 'Example command to check for suspicious files on the device: `ls -l /tmp/pwned`'}] [2]
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': 'Immediate mitigation steps include restricting access to the vulnerable OTA Online Upgrade functionality and preventing unauthorized authenticated access.'}, {'type': 'paragraph', 'content': 'Since the vulnerability requires authentication with a default administrative password "admin," changing the default password to a strong, unique password is critical.'}, {'type': 'paragraph', 'content': 'Disabling the OTA Online Upgrade feature or restricting it to trusted networks can reduce the attack surface.'}, {'type': 'paragraph', 'content': 'Monitoring and logging access to /cgi-bin/adm.cgi and the ota_new_upgrade page parameter can help detect exploitation attempts early.'}, {'type': 'paragraph', 'content': 'If possible, update the device firmware to a version that addresses this vulnerability once available from the vendor.'}, {'type': 'paragraph', 'content': 'As no known mitigations or patches are currently reported, consider replacing the affected product if immediate patching is not feasible.'}] [3, 1]