WAVLINK WN551X3-A WireGuard CLI Group ioos system os command injection
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- Proof of concept public, per CISA
- Fix
- No fix listed
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
- 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? →
- 55/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? →
- Default setups
- 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
- Exploitation: poc
- Automatable: yes
- Technical impact: total
Summary
The WAVLINK WN551X3-A router firmware is affected, specifically the WireGuard CLI group handling component in its system utility. A remote attacker who supplies a crafted group name can inject operating system commands, potentially gaining control over the device.
Read the original description
A vulnerability has been found in WAVLINK WN551X3-A M51X3_V251020-WO-182e965. This affects the function system of the file /bin/ioos of the component WireGuard CLI Group Handler. Such manipulation of the argument group_name leads to os command injection. The attack may be performed from remote. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure.
What to do
Check every install: default setups are affected.
Workaround: The checked facts list no workaround. They do state the access conditions: requests must come from loopback or carry a valid session token, and the default web password is admin.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- WAVLINK WN551X3-A
M51X3_V251020-WO-182e965
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-120344
What does this mean?
The WireGuard client-group handler in the ioos back-end of the WAVLINK WN551X3-A adds a WireGuard client group, and the checked facts say it can be reached in a way that gives full root remote code execution. The impact is described as total device compromise, theft of credentials and configuration, pivoting into the LAN, and persistent backdooring.Source: github.com
Am I affected, and how do I check?
The checked facts list firmware M51X3_V251020-WO-182e965 on the WAVLINK WN551X3-A. To check the firmware version, compare it with the version shown in the device's web admin interface or the firmware file name (_WAVLINK_WN551X3-A-M51X3_V251020-WO-182e965.bin). The handler accepts requests from loopback (127.0.0.1 IP-FROM header) or requests with a valid session token, and the default web password is listed as admin.Source: github.com
What should I do about it?
No fixed firmware version is listed in the checked facts, so no upgrade target can be given from them. Check the vendor's site for a firmware release that is newer than M51X3_V251020-WO-182e965.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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
The checked facts list no workaround. They do state the access conditions: requests must come from loopback or carry a valid session token, and the default web password is admin.Source: github.com