WAVLINK WN536AX6-A WireGuard protocol.csp wireguard_cli_group handler os command injection
Affects WAVLINK WN536AX6-A firmware V260507 in the factory default configuration with FirstLogin=1. No vendor 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 affected software is the WireGuard VPN component of the WAVLINK WN536AX6-A router firmware, specifically its web interface handler for WireGuard client group settings. Because user-supplied group identifier and name input is passed to system commands without proper sanitization, a remote attacker could potentially run arbitrary operating system commands on the device.
Read the original description
A vulnerability has been found in WAVLINK WN536AX6-A V260507. The impacted element is the function wireguard_cli_group handler of the file /protocol.csp of the component WireGuard. The manipulation of the argument group_id/group_name leads to os command injection. The attack may be initiated 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 every install: default setups are affected.
Workaround: The checked facts list no vendor fix or official workaround. The bug relies on passwordless login being enabled by default, so turning that setting off would remove the easy route to a session token, but the facts do not confirm this as an official mitigation.
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-120280
What does this mean?
The WireGuard configuration handler in the router's web interface passes the group_id and group_name values into a system command without proper filtering. A user holding a valid session token can therefore run arbitrary shell commands with root privileges.Source: github.com
Am I affected, and how do I check?
The checked facts name firmware version V260507 of the WAVLINK WN536AX6-A router, in the factory default configuration where FirstLogin=1 enables passwordless login. To check the firmware version, look at the device's admin interface or system information page. To check the FirstLogin setting, review the device configuration.Source: github.com
What should I do about it?
The checked facts do not name a fixed firmware version, so no upgrade target is known. Check the WAVLINK support channel 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 list no vendor fix or official workaround. The bug relies on passwordless login being enabled by default, so turning that setting off would remove the easy route to a session token, but the facts do not confirm this as an official mitigation.Source: github.com