HIGH 8.8

CVE-2026-13539: Wavlink WL-NU516U1-A Stack Buffer Overflow in Wireless Configuration

A stack-based buffer overflow vulnerability exists in Wavlink WL-NU516U1-A routers running firmware M16U1_V240425. An authenticated attacker can send a malicious POST request to the wireless configuration endpoint with an oversized Guest_ssid parameter, causing the application to write beyond allocated memory. This memory corruption can lead to unauthorized access, data theft, or complete device compromise. The vulnerability is remotely exploitable and public exploits are available, though the vendor has released a patched firmware version.

Source data · NVD / CISA · public domain

CVSS
3.1 · 8.8 HIGH · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weaknesses (CWE)
CWE-119, CWE-121
Affected products
0 configuration(s)
Published / Modified
2026-06-29 / 2026-06-29

NVD description (verbatim)

A vulnerability was identified in Wavlink WL-NU516U1-A M16U1_V240425. The impacted element is the function sub_407504 of the file /cgi-bin/wireless.cgi of the component POST Parameter Handler. Such manipulation of the argument Guest_ssid leads to stack-based buffer overflow. The attack can be executed remotely. The exploit is publicly available and might be used. It is suggested to upgrade the affected component. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.

6 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

The vulnerability resides in function sub_407504 within /cgi-bin/wireless.cgi, which handles POST parameters for wireless settings. The Guest_ssid parameter is not properly validated for length before being copied into a stack-allocated buffer. An attacker with valid credentials can supply a string exceeding the buffer's capacity, overwriting adjacent stack memory including return addresses and local variables. The vulnerability is classified as CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) and CWE-121 (Stack-based Buffer Overflow). CVSS v3.1 score of 8.8 (HIGH severity) reflects the combination of network accessibility, low complexity, and high impact on confidentiality, integrity, and availability.

Business impact

Compromised Wavlink routers can serve as a foothold for lateral network movement, man-in-the-middle attacks on client traffic, or staging points for broader infrastructure compromise. For organizations relying on these devices as edge network gateways or guest network controllers, exploitation could lead to data exfiltration, unauthorized network access, and disruption of wireless services. The requirement for authenticated access reduces but does not eliminate risk, as default or weak credentials are common in deployments.

Affected systems

Wavlink WL-NU516U1-A routers with firmware M16U1_V240425 are confirmed affected. The specific firmware version should be checked on deployed devices; users should verify their current firmware build against official Wavlink advisories to confirm whether they are running the vulnerable release. Other Wavlink models or firmware versions may be affected but have not been explicitly confirmed in available disclosures.

Exploitability

This vulnerability is remotely exploitable but requires valid authentication credentials to access the /cgi-bin/wireless.cgi endpoint. Public exploits are known to exist, lowering the barrier to weaponization by threat actors with network access and valid user credentials. The straightforward nature of the overflow (parameter parsing without bounds checking) and the availability of public proof-of-concept code suggest that exploitation is straightforward for any attacker with basic technical capability.

Remediation

Organizations should immediately identify and inventory Wavlink WL-NU516U1-A devices and verify their current firmware version. Wavlink has released a patched firmware version to address this vulnerability. Upgrade to the fixed firmware as soon as feasible. As an interim control, restrict administrative and wireless configuration access to trusted IP ranges or VLANs, enforce strong credentials on all router accounts, and disable remote management interfaces if not required. Monitor network traffic to these devices for suspicious POST requests to the wireless.cgi endpoint.

Patch guidance

Verify the current firmware version on each affected Wavlink device (typically found in administration settings or via SSH/telnet console). Contact Wavlink support or visit their product support portal to obtain the patched firmware version that addresses this overflow. Follow the vendor's documented firmware update procedure carefully, ensuring devices remain powered and network-connected throughout the upgrade process. Consider staging the update in a test environment first if feasible. After patching, validate device operation and document the new firmware version for compliance tracking.

Detection guidance

Monitor HTTP POST requests to /cgi-bin/wireless.cgi for unusually large or malformed Guest_ssid parameters. Intrusion detection systems should alert on payloads exceeding typical wireless SSID lengths (max 32 characters). Review web server logs on affected Wavlink devices for POST requests with parameter values that appear to contain shellcode patterns or excessive data. Monitor the device for unexpected process crashes, segmentation faults, or service restarts that could indicate exploitation attempts. Endpoint detection and response (EDR) tools on systems that manage these routers can detect abnormal process behavior following failed exploitation attempts.

Why prioritize this

Although authentication is required, the combination of public exploit availability, straightforward overflow mechanics, and the potential for complete device compromise warrants prompt patching. Wireless infrastructure devices are frequently targeted in attacks aimed at intercepting or manipulating network traffic. The HIGH CVSS score and confirmed fix availability justify prioritizing this for near-term remediation cycles.

Risk score, explained

The CVSS 8.8 score reflects a remotely exploitable vulnerability (AV:N) with low attack complexity (AC:L) that requires valid credentials (PR:L) but no user interaction (UI:N). The impact scope is unchanged (single system affected), but the attacker gains high-level access to confidentiality, integrity, and availability. The requirement for authentication prevents a higher score, but the severity remains HIGH given the criticality of router security and the existence of public exploits.

Frequently asked questions

Do I need to patch immediately if my Wavlink router isn't exposed to untrusted networks?

Yes. While this vulnerability requires authentication, credential compromise or insider threats could enable exploitation. Additionally, many organizations underestimate their actual network perimeter. Patching eliminates the risk category entirely and should be prioritized alongside other critical infrastructure updates.

Can this vulnerability be exploited without a valid user account?

No. The CVE description and attack vector (PR:L) confirm that valid authentication credentials are required to reach the vulnerable /cgi-bin/wireless.cgi endpoint. However, default or commonly known credentials on Wavlink devices should be considered a realistic attack scenario.

How do I know if my Wavlink device is vulnerable?

Check the firmware version on your device (usually found in Administration or System Settings). If it is M16U1_V240425 or earlier for the WL-NU516U1-A model, your device is confirmed vulnerable. Consult the Wavlink product security advisory for the exact patched firmware version number applicable to your hardware revision.

What happens if someone successfully exploits this vulnerability?

An attacker with valid credentials can overflow the stack buffer to overwrite function return addresses and execute arbitrary code with the privileges of the web server process on the router. This could result in complete device compromise, allowing them to modify routing rules, intercept traffic, perform denial-of-service, or pivot into the internal network.

This analysis is based on publicly disclosed information available as of 2026-06-29. Vendor and exploit availability details are subject to change. Always verify firmware version numbers and patch versions directly from the official Wavlink support channels before implementing remediation. SEC.co does not distribute, develop, or assist in the creation of exploit code or weaponized tools. Organizations should conduct internal testing to confirm patch applicability and compatibility with their specific hardware revisions and network integrations before wide-scale deployment. Source: NVD (public-domain), retrieved 2026-08-07. Analysis generated by SEC.co (claude-haiku-4-5).