Skip to main content

Wl Nu516U1 EUVDEUVD-2026-16146

| CVE-2026-4861 HIGH
Stack-based Buffer Overflow (CWE-121)
2026-03-26 VulDB
7.4
CVSS 4.0 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate to Wavlink WL-NU516U1
  2. Delivery
    Send crafted HTTP request to /cgi-bin/nas.cgi
  3. Exploit
    Manipulate Content-Length header
  4. Execution
    Trigger stack buffer overflow
  5. Impact
    Execute arbitrary code with device privileges

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2021 - Vulnerable and Outdated Components
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires authenticated access to Wavlink WL-NU516U1 (firmware 260227) with login credentials. Attacker sends crafted HTTP request with malicious Content-Length header to /cgi-bin/nas.cgi endpoint triggering stack-based buffer overflow in ftext function.

Impact

This vulnerability presents a high real-world risk despite requiring low-level authentication (PR:L). The CVSS score of 8.8 reflects network accessibility (AV:N), low attack complexity (AC:L), and complete system compromise potential (C:H/I:H/A:H). Critically, a public proof-of-concept exploit is available on GitHub, dramatically lowering the barrier to exploitation and moving the CVSS Exploit Code Maturity to 'Proof-of-Concept' (E:P). The vendor's non-responsiveness (RL:X) means no official patch is available, leaving all deployed devices vulnerable indefinitely. While authentication is required, many IoT/NAS devices use default or weak credentials, making the PR:L requirement a low barrier. The combination of public exploit code, no vendor patch, network exposure, and the typical security posture of consumer NAS devices makes this a genuine priority for organizations using affected Wavlink products.

Exploit ScenarioDerived

An attacker identifies a Wavlink WL-NU516U1 NAS device exposed to the internet or gains access to an internal network where the device resides. Using compromised low-privilege credentials (potentially obtained through credential stuffing with default passwords or phishing), the attacker sends a crafted HTTP request to /cgi-bin/nas.cgi with a maliciously oversized Content-Length header value that triggers the stack buffer overflow in the ftext function. By carefully crafting the overflow payload using the publicly available GitHub proof-of-concept, the attacker overwrites the return address on the stack to redirect execution to shellcode, gaining root-level access to the NAS device and all stored data, potentially pivoting to other network resources or exfiltrating sensitive files.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 26, 2026

Remote attackers can exploit a stack-based buffer overflow in the /cgi-bin/nas.cgi endpoint of Wavlink WL-NU516U1 by manipulating the Content-Length parameter to achieve unauthenticated remote code execution. Public exploit code is available for this vulnerability, and no patch has been released despite vendor notification. Authentication is required to trigger the flaw, limiting exposure to authenticated users or those with network access to the device.

Earlier versions of this analysis (1)
v1 Mar 26, 2026 - 08:45 CVSS 7.4

A stack-based buffer overflow vulnerability exists in the Wavlink WL-NU516U1 NAS device (version 260227) that can be exploited by sending a malicious Content-Length parameter to the /cgi-bin/nas.cgi endpoint's ftext function. The vulnerability allows authenticated remote attackers with low privileges to achieve arbitrary code execution with high impact to confidentiality, integrity, and availability (CVSS 8.8). A public proof-of-concept exploit is available on GitHub, significantly increasing the risk of active exploitation, and the vendor has been unresponsive to disclosure attempts.

RemediationAI

As the vendor (Wavlink) has not responded to vulnerability disclosure and no official patch is available, organizations should immediately isolate affected WL-NU516U1 devices from untrusted networks and the internet. Implement network segmentation to restrict access to these devices only from trusted internal IP ranges using firewall rules or VLANs. Change all default credentials to strong, unique passwords to raise the authentication barrier. Consider replacing the device with alternative NAS solutions from vendors with active security response programs if the device must remain internet-accessible. Monitor authentication logs for suspicious login attempts and implement rate limiting on the CGI interface if possible through upstream proxies or web application firewalls. Detailed exploit information is available at https://github.com/Wlz1112/WAVLINK-NU516U1-V260227/blob/main/Content-Length.md for testing defensive controls.

Affected VersionsENISA

WL-NU516U1 260227

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability affects Wavlink WL-NU516U1 network-attached storage device firmware version 260227 (CPE: cpe:2.3:a:wavlink:wl-nu516u1:*:*:*:*:*:*:*:*). The underlying issue is classified as CWE-121 (Stack-based Buffer Overflow), where the ftext function in the /cgi-bin/nas.cgi CGI script fails to properly validate the Content-Length HTTP header parameter before copying data onto the stack. This lack of bounds checking allows an attacker to overflow the stack buffer, potentially overwriting the return address and achieving arbitrary code execution. CGI-based vulnerabilities in embedded NAS devices are particularly concerning as these devices often run with elevated privileges and have direct access to sensitive file storage.

Know when Wl Nu516U1 gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 7.4 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
PoC Detected
Mar 30, 2026 - 13:26 vuln.today
Public exploit code
CVE Published
Mar 26, 2026 - 08:18 nvd
HIGH 7.4

DescriptionCVE.org

A weakness has been identified in Wavlink WL-NU516U1 260227. This vulnerability affects the function ftext of the file /cgi-bin/nas.cgi. This manipulation of the argument Content-Length causes stack-based buffer overflow. The attack can be initiated remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Executive ViewAI

Why It Matters

A critical vulnerability in Wavlink WL-NU516U1 NAS devices allows attackers with basic credentials to gain complete system control, posing immediate risk to data confidentiality, integrity, and availability. With a public exploit available and no vendor patch forthcoming, any organization using this device model is at high risk of compromise and data breach.

Business Impact: Severe
Compensating Controls

Implement WAF rules to block requests with malicious Content-Length parameters to /cgi-bin/nas.cgi; disable the ftext function if operationally feasible; segment NAS devices on isolated VLANs with strict inbound access controls; enforce multi-factor authentication for all administrative access; deploy intrusion detection signatures for known exploit patterns; consider complete device replacement as the most reliable mitigation given vendor unresponsiveness.

Threat Intelligence Overview

EPSS Score
0.0%
Top 87% exploitable
Exploit
POC
Public exploit code exists
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact
Very High
Technical Impact
Total

Priority Score

57
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +37
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy