XSS in LISTSERV 17 Web Interface (c parameter)
A cross-site scripting (XSS) vulnerability exists in the LISTSERV 17 web interface, where the 'c' parameter is not properly sanitized, allowing remote attackers to inject arbitrary JavaScript or HTML code.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows remote attackers to execute arbitrary JavaScript in the context of the user's browser session, potentially leading to session hijacking, credential theft, or other malicious actions.
If you can’t patch tonight, do this now.
As a temporary mitigation, implement input filtering and output encoding for the 'c' parameter at the web server or application level, and consider using a web application firewall (WAF) to block malicious payloads targeting this parameter.
Patch, then assume compromise.
Upgrade to a patched version of LISTSERV 17 where input validation and output encoding for the 'c' parameter have been properly implemented to prevent XSS.
No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.