WAVLINK WL-WN530BE1-A, CVE-2026-120198: a new CVE scored 10
The bottom line
If you run a WAVLINK WL-WN530BE1-A on firmware V251117, find out this week whether its web interface can be reached from outside, and cut that access first. If you have no such device, you can stop reading.
At a glance
| Fact | Detail |
|---|---|
| Product | WAVLINK WL-WN530BE1-A (CVE-2026-120198) |
| Severity | Critical: 10 (CVSS 4.0) |
| Status | A new CVE record, published by VulDB on 1 November 2026. Not on CISA's list of exploited vulnerabilities when we read it on 6 November 2026, which means nothing public says yet that anyone is using it. |
| Fixed in | No source we read names a fixed version |
| Who looks first | Anyone with a WAVLINK WL-WN530BE1-A on firmware V251117, and the IT provider who installed or manages it. The record names no other model or version. |
Does this apply to you?
| Question | If no | If yes |
|---|---|---|
| Do you run a WAVLINK WL-WN530BE1-A? | Nothing to do for this CVE. | Check the firmware version (next question). |
| Is the firmware version V251117? | The record lists only V251117; ask the vendor about your version. | Treat the device as exposed (next question). |
| Can the device's web interface be reached from the internet or by untrusted users? | Lower urgency, but still plan to fix it. | Remove that access now, then ask for a fix. |
What it is
The record says a crafted value in the group_name or IP-FROM argument of /protocol.csp lets an attacker run their own commands on the device. It says the attack can be launched remotely and that the exploit has been disclosed publicly.
Why it matters
Our reading: command injection on a network device can give an attacker control of a box that sits between your staff and the internet. The score is 10, and the record says no login is mentioned and the attack can be remote. The exploit is public, so waiting for CISA to list it is not a safe plan.
Exposure by situation
These priorities are our judgement from what the sources say about who can use the flaw and how. They are not vendor ratings.
| Your situation | Priority | Timeframe |
|---|---|---|
| A V251117 device whose web interface faces the internet | Medium | Now: remove the exposure this week |
| A V251117 device on an internal network that visitors or guests can join | Medium | This week |
| A V251117 device reachable only by trusted staff | Medium | Next patch cycle, once a fix exists |
| A WAVLINK device on another firmware version | Low | Ask the vendor; the record is silent |
| No WAVLINK WL-WN530BE1-A in the estate | None | None for this CVE |
Things people will get wrong
- "It is not on the CISA list, so nobody is using it." The record is new and not listed when read. That does not mean no one is exploiting it, and the record says the exploit is public.
- "The vendor has already patched it." No source we could read names a fixed version. The record says only that the vendor was contacted early.
- "It needs a login, so it is low risk." The description mentions no login. It says the attack can be launched remotely.
How we would triage it
This is our judgement.
Step 1: Find the devices and versions you run
- List every WAVLINK WL-WN530BE1-A, including ones installed by others.
- Read the firmware version from the device's admin page. The record names only V251117 as affected.
Step 2: Reduce exposure
- Block access to the device's web interface from the internet.
- Limit who on the internal network can reach it, because the flaw is in a web request handler.
Step 3: Ask for a fix
- Ask WAVLINK or your supplier for a fixed firmware version. No source we read names one.
- If no fix exists, ask your IT provider whether to replace the device.
Step 4: Check after the change
- Confirm from outside your network that the admin page no longer answers.
- Record the firmware version once a fix is installed.
To close it, read the version from the product itself, not from an old inventory, and save the output with the date. If you cannot update today, write down who owns it, the new date, and what limits exposure until then.
Send this to your IT provider
Copy it, change the names and dates, and send it. It is a draft for you to check, not a template tested with any provider.
Hello, we are checking exposure to CVE-2026-120198, a command injection flaw (CWE-77, CWE-74) in the WAVLINK WL-WN530BE1-A, firmware V251117. Please tell us whether we run this device, where, and which firmware version. Please confirm that its web interface is not reachable from the internet. We cannot find a fixed version in the record, so please ask the vendor for one. Please confirm the version and the fix to us in writing by the date you suggest. Thank you.
The weakness behind it
The record classes this as CWE-77 and CWE-74.
Likely ATT&CK mapping
MITRE ATT&CK is a public catalogue of the steps attackers take, from getting in to causing damage. No source has mapped this flaw to it yet, so the steps below are our prediction from what the record says the flaw allows. They are not MITRE's, the vendor's or CISA's, and an attacker may do other things.
| The step, in plain words | Stage of an attack | Why we think so |
|---|---|---|
| Command and Scripting Interpreter (T1059): Running commands or scripts on a machine, such as a shell or PowerShell. | Execution: running the attacker's code | CWE-77 identifies the core flaw as command injection; the manipulated argument is likely passed to a system shell, so successful exploitation would typically result in arbitrary OS command execution on the device. |
| Exploitation for Privilege Escalation (T1068): Using a flaw to gain higher rights than the account had, such as administrator or root. | Privilege Escalation: gaining higher rights | Web-facing processes on router firmware typically run as root; a command injection reaching that process would likely yield elevated OS privileges, making privilege escalation a probable consequence of the same exploit. |
How to use this: ask your IT provider which control or log would show each step, for example whether sign-in attempts from the internet are recorded. If nobody can answer, that is the gap to close first.
MITRE ATT&CK® is a registered trademark of The MITRE Corporation. Technique names are MITRE's.
The sources, in their words
The CVE record:
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.
Versions of WAVLINK WL-WN530BE1-A the record lists as affected:
- V251117
The record gives no version ranges. Use the vendor's advisory for the affected versions.
Check your own project
If you build software, you can compare what a project declares with this CVE from a terminal. The tool reads requirements files, package.json, Maven, Gradle, Cargo, CMake and Dockerfile files, runs nothing, and only the CVE id leaves your machine. Naming the CVEs needs no key.
lattice-scan project . --cve CVE-2026-120198Each row says in-range, outside-range, undetermined or lead, with the file and line. That is evidence about what a manifest declares, not about what runs, and a person decides. The verdicts, the CSV columns and a pipeline recipe are in the guide.
Check the servers you run
The same id can be checked against a host. Run this on the machine itself, not on the laptop that deploys to it: it reads installed packages (dpkg, rpm or apk), snaps, the hardware, the running container images with their operating system and packages, and the kernel version, compares them on the spot, and only the CVE ids leave the machine; the inventory stays on it, in ~/.lattice-scan. Naming the CVEs needs no key. Do it on each server after a deployment, and again when a new entry lands.
lattice-scan --cve CVE-2026-120198A match is a candidate for a person to confirm, not a finding. A distribution can fix a CVE under an unchanged version number, so a match is a candidate; on Debian-family hosts the report also shows whether the package's own changelog names the CVE. It reads the names of the running images, not what is inside them; for what an image declares, use the project check on its Dockerfile.
Guide: namiq.io/lattice/guides/choose-your-channel. MCP server (io.namiq/lattice in the MCP registry): namiq.io/lattice. Package: pypi.org/project/lattice-scan, or namiq.io/apt.
- Which way into Lattice fits your job →The command line, the Claude skill or the MCP server: what each needs, what works without a key and how to read the result.
- Lattice, the MCP server →The public graph the command reads, for AI agents over MCP.
- Install and connect →The signed apt repository, the fingerprint, and the connection commands for each client.
What we do not know yet
- Whether the vendor has released a fixed firmware version; no source we could read names one.
- Whether a login is required to reach the vulnerable function; the description does not say.
- Whether other WAVLINK models or firmware versions are affected; the record lists only V251117.
- Whether anyone is exploiting this in practice; the record says the exploit is public, but CISA had not listed it when read.
- Exploitation is not recorded. That is not the same as none.
- This is a new record: scores, versions and wording can change in the first days, and they are as at 6 November 2026. We have not read the vendor's advisory page and we have not tested it.
- The sections headed "The bottom line", "Does this apply to you?", "What it is", "Why it matters", "Exposure by situation", "Things people will get wrong", "Likely ATT&CK mapping", "How we would triage it" and "Send this to your IT provider" are our interpretation of the sources, not a statement by CISA or the vendor.