Multiple XSS in b2evolution 1.8.2–1.9 beta
Multiple cross-site scripting (XSS) vulnerabilities exist in b2evolution versions 1.8.2 through 1.9 beta. The vulnerabilities are present in several error handling pages, specifically in the handling of the app_name parameter in _404_not_found.page.php, _410_stats_gone.page.php, and _referer_spam.page.php, the baseurl parameter in _404_not_found.page.php, and the ReqURI parameter in _referer_spam.page.php. These parameters are not properly sanitized, allowing attackers to inject arbitrary web script or HTML.
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 or HTML in the context of the affected site, potentially leading to session hijacking, defacement, or redirection to malicious sites.
If you can’t patch tonight, do this now.
As an interim measure, restrict access to the affected error pages, implement web application firewall (WAF) rules to filter malicious input, and ensure user input is properly sanitized and output is encoded.
Patch, then assume compromise.
Upgrade to a version of b2evolution where these parameters are properly sanitized and output is correctly encoded to prevent XSS. Apply any vendor-supplied patches addressing these issues.
No validated public exploits yet. Hidden: 3 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.