CVE-2026-4544
Cross-Site Scripting in Wavlink WL-WN578W2 POST Handler
Publication date: 2026-03-22
Last updated on: 2026-04-30
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wavlink | wl-wn578w2_firmware | 221110 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
| CWE-94 | The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability impact me? :
[{'type': 'paragraph', 'content': "This vulnerability allows remote attackers to execute arbitrary scripts within the context of the router's web interface."}, {'type': 'list_item', 'content': 'Attackers can perform session hijacking by stealing authentication cookies or tokens.'}, {'type': 'list_item', 'content': 'Credential theft is possible if malicious scripts capture login information entered by users.'}, {'type': 'list_item', 'content': "Malicious actions could be triggered on behalf of the user, potentially compromising the router's security and network."}] [2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2026-4544 is a Cross-Site Scripting (XSS) vulnerability found in the WavLink WL-WN578W2 router, version V221110, specifically in the /cgi-bin/login.cgi script.'}, {'type': 'paragraph', 'content': 'The vulnerability arises because the router\'s code processes parameters such as "homepage" or "hostname" from POST requests without proper sanitization or filtering. This allows an attacker to inject malicious scripts into the router\'s web interface.'}, {'type': 'paragraph', 'content': "When a crafted POST request containing malicious script payloads is sent to the login.cgi endpoint, the router reflects these scripts in its response, enabling the execution of arbitrary JavaScript in the victim's browser."}] [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability can be detected by sending crafted POST requests to the /cgi-bin/login.cgi endpoint of the WavLink WL-WN578W2 router and observing if the response reflects injected script code without sanitization.'}, {'type': 'paragraph', 'content': "For example, you can use curl commands to test for the Cross-Site Scripting (XSS) vulnerability by injecting payloads into the 'hostname' or 'homepage' parameters and checking if the response contains the injected script."}, {'type': 'list_item', 'content': 'curl -X POST http://<router-ip>/cgi-bin/login.cgi -d "page=login&hostname=192.168.6.2\\"</script><svg/onload=alert()>" -H "Content-Type: application/x-www-form-urlencoded"'}, {'type': 'list_item', 'content': 'curl -X POST http://<router-ip>/cgi-bin/login.cgi -d "page=login&homepage=main.shtml\\"><svg/onload=alert()><" -H "Content-Type: application/x-www-form-urlencoded"'}, {'type': 'paragraph', 'content': 'If the response contains the injected script tags and triggers script execution in a browser, the vulnerability is present.'}] [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the router's web interface to trusted networks only, such as limiting access via firewall rules or network segmentation.
Avoid accessing the router's web interface from untrusted or public networks to reduce the risk of remote exploitation.
Monitor for any available firmware updates or patches from the vendor, although the vendor has not responded to this disclosure yet.
Consider disabling remote management features if enabled, to prevent remote attackers from exploiting the vulnerability.
Use strong authentication and change default credentials to reduce the risk of unauthorized access.