CVE-2026-13538: Wavlink WL-NU516U1-A Command Injection Vulnerability – Patch Available
A command injection vulnerability exists in Wavlink WL-NU516U1-A M16U1_V240425 routers. An authenticated attacker can send specially crafted POST requests to the wireless configuration endpoint (/cgi-bin/wireless.cgi) with malicious input in SSID or authentication-related parameters. This allows execution of arbitrary system commands with the privileges of the web server process. The vulnerability requires valid credentials to exploit, but the attack surface is wide since SSID and password parameters are commonly modified during normal router administration.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 6.3 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
- Weaknesses (CWE)
- CWE-74, CWE-77
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-06-29 / 2026-06-29
NVD description (verbatim)
A vulnerability was determined in Wavlink WL-NU516U1-A M16U1_V240425. The affected element is the function sub_401D68 of the file /cgi-bin/wireless.cgi of the component POST Parameter Handler. This manipulation of the argument SSID2G2/SSID5G2/AuthMethod2/WPAPSK12 causes command injection. Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized. The affected component should be upgraded. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.
10 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
The vulnerability resides in the POST parameter handler function sub_401D68 within /cgi-bin/wireless.cgi. Insufficient input validation on the SSID2G2, SSID5G2, AuthMethod2, and WPAPSK12 parameters permits command injection attacks (CWE-74, CWE-77). The vulnerable code likely passes user-supplied input directly to shell execution functions without proper sanitization or escaping. An attacker with authenticated access can inject shell metacharacters or commands that will be executed in the context of the web server process, potentially allowing lateral movement or privilege escalation depending on the process's effective permissions.
Business impact
For organizations using Wavlink routers in their network infrastructure, this vulnerability could enable an insider or compromised account holder to execute arbitrary commands on the router itself. This could lead to network traffic interception, DNS poisoning, credential harvesting, or use of the router as a pivot point into internal networks. Small businesses and branch offices that rely on these access points for perimeter security face elevated risk. The need for authentication reduces but does not eliminate the threat, especially in environments where router admin credentials may be shared or reused across devices.
Affected systems
The vulnerability specifically affects Wavlink WL-NU516U1-A model running firmware M16U1_V240425. The vendor has been responsive and released a patched version; users should verify the current firmware version on their devices and confirm availability of updates from Wavlink's support portal. Older firmware builds should be presumed vulnerable unless explicitly stated otherwise by the vendor.
Exploitability
Exploitation requires authenticated access to the router's web interface, which raises the bar above unauthenticated remote code execution. However, the exploit has been publicly disclosed, meaning proof-of-concept code or techniques are available in the wild. Organizations with weak admin password policies or exposed management interfaces are at higher risk. The attack complexity is low once credentials are obtained, and there are no user interaction requirements.
Remediation
The primary remediation is to upgrade to the patched firmware version released by Wavlink. Administrators should check Wavlink's official website or the device management portal for the latest firmware build. In the interim, enforce strong, unique credentials on all router administrative accounts; restrict web management interface access to trusted IP addresses or VPNs; and monitor for suspicious POST requests to /cgi-bin/wireless.cgi. Isolate affected devices from sensitive network segments if patching is delayed.
Patch guidance
Contact Wavlink support or check their official firmware download page to obtain the fixed version for the WL-NU516U1-A. The vendor was noted as responsive and professional in handling this disclosure, so updates should be available. Verify the firmware build number after installation to confirm the patch has been applied. Document the patching activity in your change management system, especially if you have multiple units of this model.
Detection guidance
Monitor network traffic for POST requests to /cgi-bin/wireless.cgi with unusual parameter values or shell metacharacters (backticks, pipes, semicolons, $(), etc.) in the SSID2G2, SSID5G2, AuthMethod2, or WPAPSK12 fields. Enable router access logs if available and review them for POST requests from unusual source IPs or at odd times. Intrusion detection signatures should flag payloads containing command substitution syntax in wireless configuration requests. Alert on multiple failed configuration attempts followed by a successful one, as attackers may probe the endpoint before executing a payload.
Why prioritize this
While the CVSS score of 6.3 (MEDIUM) reflects the authentication requirement, the public disclosure and ease of exploitation once authenticated warrant prioritization in environments where router admin access is not tightly controlled. Organizations using these routers for critical network functions should patch urgently. Those with strong credential and access controls can accept a brief delay, but should still plan remediation within their standard patch cycle. The responsive vendor posture suggests patches should be readily available.
Risk score, explained
The CVSS 3.1 score of 6.3 is based on network-accessible attack vector (AV:N), low attack complexity (AC:L), and the requirement for low-privilege authentication (PR:L). It yields low confidentiality, integrity, and availability impact (C:L/I:L/A:L) within the scope of the router itself. The score would be significantly higher if the vulnerability permitted unauthenticated exploitation. However, in practical terms, organizations should consider their specific risk tolerance, network segmentation, and the likelihood of credential compromise when prioritizing this against other vulnerabilities.
Frequently asked questions
Do I need to patch immediately, or can this wait?
If your routers are isolated on a management network with strong access controls and monitored for suspicious activity, you have a short grace period to plan patching during a maintenance window. However, given the public disclosure and relative ease of exploitation by an authenticated attacker, prioritize patching within 1–2 weeks. If your routers are accessible from guest networks, untrusted VLANs, or you cannot confirm the strength of admin credentials, patch immediately.
What should I do if I do not have access to a patched firmware version yet?
Contact Wavlink support directly for availability of the fixed firmware. In the interim, restrict administrative access to your routers by IP whitelist, require VPN access before allowing management interface connections, enforce multi-factor authentication if available, and rotate admin passwords. Monitor access logs carefully for signs of exploitation. Consider temporarily isolating the affected routers from production traffic if your architecture permits.
Can an attacker exploit this without credentials?
No, the vulnerability requires authenticated access to the router's web interface. However, if an attacker has compromised a user account or obtained credentials through phishing or other means, they can then exploit this vulnerability to achieve code execution. This is why credential hygiene—strong, unique passwords and access restrictions—is critical.
Which Wavlink routers are affected, and are there other models vulnerable to similar issues?
This advisory specifically addresses the WL-NU516U1-A running firmware M16U1_V240425. While we do not have visibility into other Wavlink products at this time, you should check Wavlink's security announcements and your device firmware version to confirm whether you are running the vulnerable build. If you have multiple Wavlink devices in your environment, apply the same credential and access control hardening measures across all of them as a precaution.
This analysis is provided for informational purposes and should not substitute for professional security assessment, vendor advisories, or your organization's own risk evaluation. Always verify firmware version numbers and patch availability directly from the vendor's official channels. Exploitation techniques and proof-of-concept code are not provided in this advisory. Organizations should conduct their own testing in non-production environments before deploying patches. SEC.co assumes no liability for impacts arising from application of this guidance or failure to patch. Source: NVD (public-domain), retrieved 2026-08-07. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-10060MEDIUMTRENDnet TEW-432BRP Command Injection—End-of-Life Router Vulnerability
- CVE-2026-10061MEDIUMTRENDnet TEW-432BRP Command Injection Vulnerability – Remediation via Replacement
- CVE-2026-10127MEDIUMEdimax BR-6478AC Command Injection in Firmware 1.23
- CVE-2026-10166MEDIUMEdimax BR-6478AC Command Injection – Authentication Required
- CVE-2026-10180MEDIUMTRENDnet TEW-432BRP Command Injection Vulnerability – Hardware Retirement Required
- CVE-2026-10182MEDIUMTRENDnet TEW-432BRP Command Injection – Unpatched EOL Device
- CVE-2026-10550MEDIUMCommand Injection in elunez eladmin Deployment Module
- CVE-2026-10878MEDIUMD-Link DWR-M920 Command Injection Vulnerability – Patch Now