WAVLINK WN536AX6-A Web Management ioos sub_416760 os command injection
Only affects WAVLINK WN536AX6-A devices running firmware M36AX6_V260507_2.0.0-WO-d173724. The checked facts list no fix.
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? →
- 37/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
Summary
The WAVLINK WN536AX6-A router's web management interface, specifically its /bin/ioos component, contains a flaw that lets a remote attacker inject operating system commands through the group_name input. Successful exploitation could allow an attacker to run arbitrary commands on the affected device.
Read the original description
A weakness has been identified in WAVLINK WN536AX6-A V260507_2.0.0. This vulnerability affects the function sub_416760 of the file /bin/ioos of the component Web Management Interface. This manipulation of the argument group_name causes os command injection. It is possible to initiate the attack remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure.
What to do
Check every install: default setups are affected.
Workaround: No vendor workaround is listed in the checked facts. The described paths depend on reaching the back-end on port 81 and on a device still in factory-default first_login state, so keeping the router off untrusted networks and completing first-time setup are the only related points the facts support.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- WAVLINK WN536AX6-A
V260507_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-120276
What does this mean?
The router's web management component passes attacker-supplied input to operating system commands, which can run as root on the device. The advisory describes this as full remote code execution, allowing persistent backdoors, credential and config theft, and pivoting into the LAN.Source: github.com
Am I affected, and how do I check?
The checked facts name firmware M36AX6_V260507_2.0.0-WO-d173724 of the WN536AX6-A. The attack needs either loopback or SSRF reachability of the ioos back-end on port 81, or any valid session token. A factory-default device in first_login state, whose login accepts an empty password, is also described. The firmware build string can be compared against the device's reported firmware version.Source: github.com
What should I do about it?
The checked facts list no fixed firmware version, so no upgrade target can be given. Check the vendor for a fixed build before treating the device as patched.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?
No vendor workaround is listed in the checked facts. The described paths depend on reaching the back-end on port 81 and on a device still in factory-default first_login state, so keeping the router off untrusted networks and completing first-time setup are the only related points the facts support.Source: github.com