Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach device web interface over network
-
DeliveryForge IP-FROM:127.0.0.1 header to bypass login
-
ExploitInject shell metacharacters via file_id in ovpn_file del request
-
ExecutionUnsanitized input reaches popen()
-
ImpactExecute arbitrary commands as root
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization OS command sanitization, avoid shell exec
MITRE ATT&CK
2 techniques 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 | Exploitation requires network reachability to the device's web management service (/protocol.csp handler in the ioos binary) and an HTTP request to opt=ovpn_file with type=del carrying a malicious file_id value. The critical enabling condition is the authentication-bypass flaw: the device trusts a client-supplied 'IP-FROM: 127.0.0.1' header as proof of localhost origin, so an attacker simply forges that header to defeat login - no credentials, no user interaction, and the device's default web interface is sufficient. The main limiting factor is exposure: the attacker must be able to reach the device's HTTP interface (LAN-adjacent, or WAN-exposed if remote management is reachable), and the target must run firmware at or below M30BE1_V251117. No special non-default configuration is needed beyond the device operating normally. |
| Impact | This is a genuine high-priority issue, not a CVSS-inflated paper risk. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes network-reachable, low-complexity, unauthenticated exploitation with no user interaction and full high impact to confidentiality, integrity and availability (VC:H/VI:H/VA:H) - and the description corroborates every one of those metrics: a remote attacker forges an 'IP-FROM: 127.0.0.1' header to bypass login and reaches popen() as root. The signals are internally consistent rather than conflicting. A public POC exists (hosted on GitHub and referenced by VulnCheck), which materially raises the likelihood of opportunistic use, but there is NO CISA KEV listing and NO EPSS score in the provided data, so active in-the-wild exploitation is not confirmed and real-world exploitation volume cannot be quantified from these inputs. The practical risk ceiling is strongly moderated by product prevalence: this is a niche consumer Wi-Fi range extender, so widespread automated mass-exploitation is less likely than targeted or botnet-style scanning of exposed devices. Net: treat as urgent for any environment that actually runs this device with its web interface exposed, while recognizing the limited deployment footprint. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker sends a single crafted HTTP request to /protocol.csp?opt=ovpn_file with type=del, including a forged 'IP-FROM: 127.0.0.1' header to defeat the login check, and embeds shell metacharacters in the file_id parameter that the ioos binary passes unsanitized to popen(). Because execution occurs as root, the attacker gains full device takeover from one request. A public proof-of-concept is already available, so weaponization effort is minimal and the attack can be scripted against internet- or LAN-exposed devices. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 20, 2026
Unauthenticated OS command injection in Wavlink WL-WN530BE1-A firmware through M30BE1_V251117 lets remote attackers execute arbitrary commands as root by forging an IP-FROM: 127.0.0.1 header to bypass login and supplying a crafted file_id parameter to /protocol.csp?opt=ovpn_file with type=del. Publicly available exploit code exists, and the VulnCheck advisory plus a public write-up describe the flaw; no CISA KEV confirmation was provided. The assessed CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, making this a high-priority exposure when the management interface is reachable.
RemediationAI
No vendor-released patch was identified in the provided data; check Wavlink and the VulnCheck advisory at https://www.vulncheck.com/advisories/wavlink-wl-wn530be1-a-unauthenticated-os-command-injection-in-ioos-protocol-csp-ovpn-file-handler for a firmware update and apply it as soon as an M30BE1 build later than V251117 is published. Until then, restrict the device's HTTP management interface to trusted LAN segments or a VPN, and block WAN access to the web UI - trade-off: remote administration becomes unavailable unless tunneled. Add firewall or reverse-proxy rules that reject external requests to /protocol.csp and drop requests carrying IP-FROM: 127.0.0.1 from untrusted networks, since the device treats that header as localhost proof; trade-off: legitimate local health checks or integrations using that header may break. Disable remote management if it is enabled and segment IoT/router management traffic from user networks; monitor logs for unusual opt=ovpn_file&type=del requests. These are compensating controls only, not a substitute for firmware remediation.
Affected VersionsENISA
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 is a CWE-78 OS command injection in the ioos binary of Wavlink WL-WN530BE1-A firmware, specifically in the sub_23B54 function, which passes the unsanitized file_id parameter from /protocol.csp?opt=ovpn_file requests with type=del into popen(). The critical enabling weakness is an authentication bypass: the firmware trusts a client-supplied IP-FROM: 127.0.0.1 header as evidence that the request originated from localhost, so a remote attacker can forge that header and reach the vulnerable handler without credentials. The affected CPE is cpe:2.3:a:wavlink:wl-wn530be1-a:*:*:*:*:*:*:*:*, covering firmware through M30BE1_V251117. Public analysis is available in the VulnCheck advisory and a GitHub write-up, and the provided CVSS 4.0 score is 9.3 while the independent assessment uses CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
Know when Wl Wn530Be1 A 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
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Forged header bypasses auth so PR:N; single network request with no user interaction gives AV:N/AC:L/UI:N; root command execution yields C:H/I:H/A:H with no scope change.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
Wavlink WL-WN530BE1-A firmware through M30BE1_V251117 contains an OS command injection vulnerability in the sub_23B54 function of the ioos binary, which passes the unsanitized file_id parameter of /protocol.csp?opt=ovpn_file requests with type=del to popen(). A remote unauthenticated attacker can send a forged IP-FROM: 127.0.0.1 header to bypass login and execute arbitrary commands as root.
Technical POC Analysis
CWE-78 OS command injection in sub23B54 of the ioos binary.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Latest POC
1 PoC candidate from github (unverified)
Sign in to open the public PoC links collected for this CVE.
Executive ViewAI
Wavlink WL-WN530BE1-A wireless routers running firmware M30BE1_V251117 and earlier contain a critical flaw that lets anyone who can reach the device's web management interface take full root-level control without credentials. Because publicly available exploit code exists and Wavlink has not released a fixed firmware image, every unit still in service is a standing exposure - and these devices typically sit at the network edge, where compromise gives an intruder a durable foothold for intercepting traffic, harvesting credentials, and pivoting into internal segments. Leadership should care because the risk is not confined to the router itself: unmanaged or forgotten units in branch offices, retail sites, or executive home offices can silently become an entry point that bypasses perimeter defenses, and the absence of a patch means the exposure will persist until devices are isolated or replaced.
No vendor-released patch identified at time of analysis. Interim mitigations: remove internet-facing exposure of the WL-WN530BE1-A management interface and restrict /protocol.csp access to a dedicated, tightly scoped management VLAN; disable remote and cloud management, UPnP, and any WAN-side administrative services; front the devices with a WAF/IPS rule blocking requests to opt=ovpn_file and any request containing an IP-FROM header; monitor for the IP-FROM: 127.0.0.1 bypass pattern and for unexpected outbound sessions or configuration changes; rotate credentials and VPN material associated with affected devices; and replace units that cannot be segmented and monitored with vendor-supported hardware.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
More in Wl Wn530Be1 A
View allStack-based buffer overflow in the Wavlink WL-WN530BE1-A router (firmware build 251117) allows remote compromise of the
Command injection in the Wavlink WL-WN530BE1-A wireless router (firmware 251117) allows an authenticated, low-privileged
EUVD-2026-105226
GHSA-j6fh-9747-5rv9
NVD
CVE.org
EPSS
Exploit-DB