WAVLINK WL-WN530BE1-A protocol.csp con_check_read_finish command injection
Affects WAVLINK WL-WN530BE1-A running firmware M30BE1_V251117, where a crafted request to protocol.csp can run commands as root. CVSS scores it 10 (critical), and no fix is listed yet.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 22/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The WAVLINK WL-WN530BE1-A wireless router's web management interface contains a flaw in its protocol.csp handler that lets a remote attacker inject operating system commands through crafted input fields. Successful exploitation could allow an attacker to run arbitrary commands on the device, potentially taking control of the router and the network it manages.
Read the original description
A vulnerability has been found in WAVLINK WL-WN530BE1-A V251117. Affected is the function con_check_read_finish of the file /protocol.csp. Such manipulation of the argument group_name/IP-FROM leads to command injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure.
What to do
Workaround: The checked facts list no fix and no workaround. Until a fix is published, the checked sources give no mitigation beyond watching for a firmware update from WAVLINK.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- WAVLINK WL-WN530BE1-A
V251117
Evidence 5
- Advisory
- Advisory
- Advisory
- Advisory
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120198
What does this mean?
The ioos binary that handles /protocol.csp skips the login check when the client sends an IP-FROM header equal to 127.0.0.1. A crafted request to the WireGuard client-group add function then runs arbitrary commands as root and can give an interactive shell, with access to files such as /etc/shadow, Wi-Fi credentials and VPN certificates.Source: github.com
Am I affected, and how do I check?
The affected firmware is M30BE1_V251117 on the WAVLINK WL-WN530BE1-A router. To check, read the Firmware Version shown in the router's firmware information. The bug is in requests to /protocol.csp with opt=wireguard_cli_group, function=set and action=add.Source: github.com
What should I do about it?
The checked facts do not name a fixed firmware version or an upgrade target. Check the WAVLINK vendor site for a newer firmware release that changes this firmware version.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
The checked facts list no fix and no workaround. Until a fix is published, the checked sources give no mitigation beyond watching for a firmware update from WAVLINK.Source: github.com