WAVLINK WN553X1-B WireGuard CLI Group ioos sub_41A748 os command injection
Affects WAVLINK WN553X1-B firmware V260403_2.0.0, reached through the WireGuard CLI group action=add endpoint and requiring a valid session token. No fix is listed.
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? →
- Specific setups only
- 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 WN553X1-B router firmware is affected, specifically the WireGuard CLI group handler in its /bin/ioos component. A remote attacker who manipulates the group_id or group_name input could inject operating system commands, potentially gaining control over the device.
Read the original description
A vulnerability was determined in WAVLINK WN553X1-B V260403_2.0.0. This issue affects the function sub_41A748 of the file /bin/ioos of the component WireGuard CLI Group Handler. Executing a manipulation of the argument group_id/group_name can lead to os command injection. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure.
What to do
Check whether your setup matches what the bug needs.
Affected firmware V260403_2.0.0 of WAVLINK WN553X1-B Triggered through the action=add branch of the wireguard_cli_group endpoint A valid session token is requiredWorkaround: The checked facts list no workaround or vendor fix. The only stated precondition is a valid session token, so the vendor's guidance should be checked for any further steps.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- WAVLINK WN553X1-B
V260403_2.0.0
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-120240
What does this mean?
The add action of the WireGuard CLI group endpoint passes the group_id and group_name parameters to snprintf without validation or sanitization. An authenticated user can use this to run arbitrary OS commands as root, which fully compromises the device.Source: github.com
Am I affected, and how do I check?
Firmware V260403_2.0.0 (OpenWrt 21.02, aarch64 / MT7981) of the WAVLINK WN553X1-B is listed as affected, through the action=add branch of the wireguard_cli_group endpoint. Compare the firmware version shown on the device with this build to see whether it matches.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 advisory for a fixed release before deciding on an update.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 workaround or vendor fix. The only stated precondition is a valid session token, so the vendor's guidance should be checked for any further steps.Source: github.com