VulnerabilityPublished 22 Mar 2026Updated 23 Mar 2026

CVE-2026-4544: Wavlink WL-WN578W2 · Cross-site Scripting

Affects Wavlink WL-WN578W2Source CVE Database V5

Public exploit available · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

4.8Medium

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

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

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
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: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within 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: None: There is no impact to availability within 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 22 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

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 or the CVSS exploit maturity 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-WN578W2	Affected =221110	Fixed in–

AI-suggested

Given the absence of official patches, organizations should implement the following specific mitigations: 1) Restrict access to the router’s web management interface by limiting it to trusted internal networks only, using firewall rules or network segmentation. 2) Disable remote management features if not strictly necessary to reduce exposure to the internet. 3) Employ web filtering or endpoint protection to block access to known malicious URLs that could be used in social engineering attacks exploiting this XSS. 4) Educate users and administrators about the risks of clicking unsolicited links or visiting untrusted websites while logged into the router’s interface. 5) Monitor network traffic and router logs for unusual activity that may indicate exploitation attempts. 6) Consider replacing affected devices with models from vendors that provide timely security updates. 7) If feasible, implement web application firewalls (WAFs) or reverse proxies that can sanitize or block malicious POST requests targeting the vulnerable endpoint. 8) Regularly review and update router firmware to the latest versions once the vendor releases a patch addressing this vulnerability.

Description

A vulnerability was determined in Wavlink WL-WN578W2 221110. This affects an unknown function of the file /cgi-bin/login.cgi of the component POST Request Handler. Executing a manipulation of the argument homepage/hostname/login_page can lead to cross site scripting. It is possible to launch the attack remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The primary impact of CVE-2026-4544 is the potential compromise of the web management interface of the Wavlink WL-WN578W2 router. Successful exploitation can lead to session hijacking, credential theft, or unauthorized actions performed with the privileges of the logged-in user. This can result in attackers gaining persistent access to the router’s configuration, enabling further network compromise or surveillance. Although the vulnerability does not directly affect device availability or confidentiality of stored data, the integrity of the management interface is compromised, which can cascade into broader network security risks. Organizations relying on this router for critical network functions, especially those with remote management enabled, face increased risk of targeted attacks. The lack of vendor response and patches prolongs exposure, increasing the window for attackers to develop and deploy exploits. The requirement for user interaction limits automated mass exploitation but does not eliminate risk, particularly in environments where users may be socially engineered. Overall, the threat could facilitate lateral movement within networks and undermine trust in network infrastructure devices.

Summary

CVE-2026-4544 identifies a cross-site scripting (XSS) vulnerability in the Wavlink WL-WN578W2 router firmware version 221110. The vulnerability resides in the POST request handler of the /cgi-bin/login.cgi endpoint, specifically involving the manipulation of the homepage/hostname/login_page parameter. An attacker can craft a malicious POST request that injects executable script code into the web interface, which is then executed in the context of the victim’s browser when interacting with the login page. This XSS flaw is remotely exploitable without requiring prior authentication, but it does require user interaction, such as clicking a crafted link or visiting a malicious page. The vulnerability does not affect the confidentiality or availability of the device directly but can compromise the integrity of the web session, enabling attackers to steal session cookies, perform actions on behalf of the user, or redirect users to malicious sites. The vendor was notified early but has not issued any patches or advisories, leaving the vulnerability unmitigated. The CVSS 4.0 base score is 4.8, reflecting medium severity due to the ease of remote exploitation balanced against the need for user interaction and limited impact scope. No known exploits have been observed in the wild yet, but public disclosure increases the risk of exploitation attempts. This vulnerability affects organizations using this specific Wavlink router model, especially those exposing the device’s web interface to untrusted networks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Mar 2026, 00:04 UTC

Technical details

References

Community reviews

Related threats