WAVLINK WN553X1-B WireGuard CLI ioos sub_419DA8 os command injection
Affects WAVLINK WN553X1-B firmware V260403_2.0.0 through a request using action=close in the WireGuard CLI. CVSS 9.4 (critical); no vendor rating or fix is listed in the checked facts.
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, specifically its WireGuard command-line handler component, is affected by this vulnerability. A remote attacker could exploit improper input handling in the file_id argument to inject and run arbitrary operating system commands on the device.
Read the original description
A vulnerability was found in WAVLINK WN553X1-B V260403_2.0.0. This vulnerability affects the function sub_419DA8 of the file /bin/ioos of the component WireGuard CLI Handler. Performing a manipulation of the argument file_id results in os command injection. The attack is possible to be carried out remotely. The exploit has been made public and could be used. 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 on WAVLINK WN553X1-B The request must use action=close to reach the vulnerable branchWorkaround: The checked facts list no fix and no workaround. Because the attacker must be authenticated, limiting who can log in to the device's management interface would reduce exposure.
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-120239
What does this mean?
An authenticated attacker can run arbitrary OS commands with root privileges through the WireGuard CLI, which gives full control of the device.Source: github.com
Am I affected, and how do I check?
The checked facts name firmware V260403_2.0.0 (OpenWrt 21.02, aarch64 / MT7981) on the WAVLINK WN553X1-B. The bug is reached only through a request that uses action=close. Compare the firmware version on the device with V260403_2.0.0.Source: github.com
What should I do about it?
The checked facts do not name a fixed version or an upgrade target.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. Because the attacker must be authenticated, limiting who can log in to the device's management interface would reduce exposure.Source: github.com