WAVLINK WN536AX6-A OpenVPN protocol.csp strcpy stack-based overflow
Affects WAVLINK WN536AX6-A firmware V260507 in the factory default configuration with passwordless login enabled. No fix is listed in the checked facts.
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 wireless router's OpenVPN handler component (in its protocol.csp file) is affected by this vulnerability. An attacker who can reach the device over the network could send a crafted OpenVPN IP value that overflows a stack buffer, potentially crashing the device or allowing arbitrary code to run on it.
Read the original description
A vulnerability was found in WAVLINK WN536AX6-A V260507. This affects the function strcpy of the file /protocol.csp of the component OpenVPN Handler. The manipulation of the argument openvpn_ip results in stack-based buffer overflow. The attack may be launched remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure.
What to do
Check every install: default setups are affected.
Workaround: The checked facts list no workaround. Check the vendor's advisory for mitigations. The facts do not say that changing the passwordless login setting removes the risk.
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-120281
What does this mean?
A stack-based buffer overflow in the openvpn_ser handler of /protocol.csp uses an unsafe strcpy. The facts say an unauthenticated attacker can crash the web backend process (denial of service) or possibly run code as root.Source: github.com
Am I affected, and how do I check?
The checked facts list firmware V260507 of the WAVLINK WN536AX6-A. The bug needs the factory default configuration with FirstLogin=1 and passwordless authentication enabled. Compare your firmware version and login settings against these conditions.Source: github.com
What should I do about it?
The checked facts name no fixed version, so no upgrade target is available from them. Check the vendor's site for a firmware update that fixes this issue.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. Check the vendor's advisory for mitigations. The facts do not say that changing the passwordless login setting removes the risk.Source: github.com