WAVLINK WN553X1-B ioos sub_416B50 os command injection
Affects WAVLINK WN553X1-B running firmware V260403_2.0.0, where an authenticated user holding a valid session token can run commands as root. 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? →
- 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 "ioos" binary's handling of the file_id argument. A remote attacker could exploit this to inject operating system commands, potentially gaining control of the device.
Read the original description
A vulnerability has been found in WAVLINK WN553X1-B 260403_2.0.0. This issue affects the function sub_416B50 of the file /bin/ioos. The manipulation of the argument file_id leads to os command injection. The attack is possible to be carried out remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure.
What to do
Check whether your setup matches what the bug needs.
Attacker needs an authenticated session token Affected firmware V260403_2.0.0 on WAVLINK WN553X1-B Session token is bound to the client IP and expires after 300 secondsWorkaround: The checked facts list no workaround. Limiting who can log in to the device's management interface would reduce exposure, since the attack depends on an authenticated session.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- WAVLINK WN553X1-B
260403_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-120229
What does this mean?
A function in the device's ioos firmware (sub_416B50) passes attacker-supplied input to the operating system shell without proper checks. This lets an attacker run arbitrary commands with root privileges, which gives full control of the device.Source: github.com
Am I affected, and how do I check?
The listed affected version is firmware V260403_2.0.0 (OpenWrt 21.02, aarch64 / MT7981) on the WN553X1-B. The attack requires an authenticated session token that is bound to the client IP and expires after 300 seconds. To check the firmware version, look at the firmware information on the device's admin interface.Source: github.com
What should I do about it?
The checked facts do not name a fixed firmware version, so no upgrade target is available from them. Check the vendor's support channels for a patched firmware release.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. Limiting who can log in to the device's management interface would reduce exposure, since the attack depends on an authenticated session.Source: github.com