WAVLINK WN553X1-B ovpn_file ioos sub_4162A8 os command injection
Affects WAVLINK WN553X1-B firmware V260403_2.0.0 (OpenWrt 21.02, aarch64 / MT7981) with a valid session token. No 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 is affected, specifically its OpenVPN file handling component. A remote attacker can manipulate an input parameter to run arbitrary operating system commands on the device, potentially taking full control of it.
Read the original description
A vulnerability has been found in WAVLINK WN553X1-B 260403_2.0.0. This affects the function sub_4162A8 of the file /bin/ioos of the component ovpn_file Handler. Such manipulation of the argument file_id leads to os command injection. The attack can be executed 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.
Firmware V260403_2.0.0 of WAVLINK WN553X1-B A valid session token is required Request must use function=set and type=del on the ovpn_file endpointWorkaround: The checked facts list no workaround or vendor fix. Until one is published, limiting who can log in to the device's web interface reduces the chance of the required authenticated access.
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-120238
What does this mean?
The ovpn_file endpoint does not properly handle input in one of its requests, so a logged-in attacker can run arbitrary OS commands as root, which can fully compromise the device.Source: github.com
Am I affected, and how do I check?
The listed affected firmware is V260403_2.0.0 of the WAVLINK WN553X1-B (OpenWrt 21.02, aarch64 / MT7981). The attack needs a valid session token and a request using function=set and type=del on the ovpn_file endpoint. Compare the firmware version shown on the device with the listed version.Source: github.com
What should I do about it?
The checked facts name no fixed firmware version, so no upgrade target can be given. Check the vendor's site for a newer 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 or vendor fix. Until one is published, limiting who can log in to the device's web interface reduces the chance of the required authenticated access.Source: github.com