CVE-2026-2530VulnerabilityPublished 16 Feb 2026Updated 23 Feb 2026

CVE-2026-2530: Wavlink WL-WN579A3 · Command Injection

Affects Wavlink WL-WN579A3Source CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 9.1% chance of exploitation in 30 days – higher than 95% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
WavlinkWL-WN579A3	Affected =20210219	Fixed in–

AI-suggested

Given the absence of vendor patches, organizations should implement several specific mitigations to reduce risk. First, isolate the Wavlink WL-WN579A3 devices on segmented network zones with strict firewall rules limiting remote access to the device management interface, especially blocking access to /cgi-bin/wireless.cgi from untrusted networks. Disable remote management features if not required. Monitor network traffic for unusual requests targeting the macAddr parameter or the wireless.cgi endpoint. Employ intrusion detection/prevention systems (IDS/IPS) with signatures for command injection attempts. Where possible, replace affected devices with models from vendors with active security support. If replacement is not immediately feasible, consider deploying network-level application firewalls or reverse proxies to sanitize input to the vulnerable CGI endpoint. Regularly audit device configurations and logs for signs of compromise. Maintain an inventory of affected devices and track any future vendor advisories. Finally, educate network administrators about this vulnerability to ensure rapid response if exploitation attempts are detected.

Description

A weakness has been identified in Wavlink WL-WN579A3 up to 20210219. This affects the function AddMac of the file /cgi-bin/wireless.cgi. This manipulation of the argument macAddr causes command injection. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The impact of CVE-2026-2530 is significant for organizations using the Wavlink WL-WN579A3 router. Successful exploitation allows remote attackers to execute arbitrary commands on the device without authentication, potentially leading to full device compromise. This can result in unauthorized network access, interception or manipulation of network traffic, disruption of network services, and use of the device as a foothold for lateral movement within internal networks. Confidentiality is at risk as attackers may capture sensitive data traversing the router. Integrity can be compromised by altering device configurations or injecting malicious payloads. Availability may be affected if attackers disrupt or disable network connectivity. The lack of vendor patches increases exposure duration, raising the likelihood of exploitation. Organizations relying on this router in critical infrastructure, enterprise, or home environments face elevated risks of data breaches, service outages, and reputational damage. The medium CVSS score reflects the balance between ease of exploitation and the scope of impact, but the real-world consequences could be severe if exploited in targeted attacks.

Summary

CVE-2026-2530 is a command injection vulnerability identified in the Wavlink WL-WN579A3 wireless router, specifically affecting firmware versions up to 20210219. The vulnerability resides in the AddMac function of the /cgi-bin/wireless.cgi script, which processes the macAddr parameter. Improper input validation allows an attacker to inject arbitrary shell commands by manipulating this parameter. Because the vulnerable CGI endpoint is accessible remotely and does not require authentication or user interaction, an attacker can exploit this flaw over the network to execute commands with the privileges of the web server process. This could lead to full compromise of the device, enabling attackers to alter configurations, intercept or redirect traffic, or pivot into internal networks. The vendor was notified early but has not issued any patches or advisories, leaving devices exposed. The vulnerability has a CVSS 4.0 score of 5.3, reflecting medium severity due to the ease of exploitation and potential impact on device security. Although no active exploitation has been reported, public exploit code availability increases the risk of future attacks. The lack of vendor response and patch availability exacerbates the threat, requiring users to implement alternative mitigations. This vulnerability highlights the risks of insecure input handling in embedded device web interfaces and the critical need for vendor responsiveness in vulnerability management.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 21:16 UTC

Technical details

References

Community reviews

Related threats