WAVLINK WN536AX6-A openvpn_cli protocol.csp os command injection
Affects WAVLINK WN536AX6-A firmware V260507 in the factory default configuration with FirstLogin=1, which enables passwordless authentication. The checked facts list no fix.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Published
- 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 firmware is affected, specifically the openvpn_cli handler in its protocol.csp component. A remote attacker can manipulate the file_id argument to inject operating system commands, potentially giving them control over the device.
Read the original description
A flaw has been found in WAVLINK WN536AX6-A V260507. The affected element is an unknown function of the file /protocol.csp of the component openvpn_cli Handler. Executing a manipulation of the argument file_id can lead to os command injection. The attack can be launched remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure.
What to do
Check every install: default setups are affected.
Workaround: The checked facts do not describe a workaround. The flaw depends on the factory default FirstLogin=1 passwordless setting, so the vendor's guidance on that setting is the first thing to check while no fix is available.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- WAVLINK WN536AX6-A
V260507
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-120279
What does this mean?
The openvpn_cli protocol.csp component passes input to an operating system command without proper neutralization. The flaw allows arbitrary shell commands to run on the device as root, which can lead to full device compromise.Source: github.com
Am I affected, and how do I check?
The checked facts name firmware V260507 of the WAVLINK WN536AX6-A, under the factory default configuration with FirstLogin=1, which enables passwordless authentication. To check, look at the firmware version on the device's admin interface and whether FirstLogin is set to 1.Source: github.com
What should I do about it?
The checked facts do not name a fixed firmware version to upgrade to. Check the vendor's support channels for an updated 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 do not describe a workaround. The flaw depends on the factory default FirstLogin=1 passwordless setting, so the vendor's guidance on that setting is the first thing to check while no fix is available.Source: github.com