CVE-2026-6559
Received Received - Intake
Cross-Site Scripting in Wavlink WL-WN579A3 Login CGI

Publication date: 2026-04-19

Last updated on: 2026-04-19

Assigner: VulDB

Description
A weakness has been identified in Wavlink WL-WN579A3 220323. This affects the function sub_401F80 of the file /cgi-bin/login.cgi. This manipulation of the argument Hostname causes cross site scripting. Remote exploitation of the attack is possible. Upgrading the affected component is recommended. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-19
Last Modified
2026-04-19
Generated
2026-05-07
AI Q&A
2026-04-19
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
wavlink wl-wn579a3 220323
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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
Can you explain this vulnerability to me?

This vulnerability exists in the Wavlink WL-WN579A3 device, specifically in the function sub_401F80 of the file /cgi-bin/login.cgi. It involves manipulation of the Hostname argument, which leads to a cross-site scripting (XSS) vulnerability. This means an attacker can remotely exploit this flaw to inject malicious scripts.


How can this vulnerability impact me? :

The vulnerability allows remote attackers to perform cross-site scripting attacks by manipulating the Hostname argument. This can lead to the execution of malicious scripts in the context of the affected device's web interface, potentially compromising user interactions or session integrity. However, the impact is limited to integrity, with no direct confidentiality or availability impact noted.


What immediate steps should I take to mitigate this vulnerability?

The recommended immediate step to mitigate this vulnerability is to upgrade the affected component to the fixed version released by the vendor.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart