CVE-2024-33326: A Cross-site Scripting (XSS)
Source CVE Database V5
Not known to be exploited · public detection template (Nuclei) · CVSS 6.1 Medium.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 26 Jun 2024
Detectable: evidence found.
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
To mitigate CVE-2024-33326, organizations should implement strict input validation and output encoding on the lumPageID parameter to neutralize malicious payloads. Employing a web application firewall (WAF) with rules to detect and block XSS attack patterns targeting this parameter can provide immediate protection. Security teams should monitor web server logs for suspicious requests containing unusual or encoded scripts in the lumPageID parameter. User awareness training to recognize and avoid clicking suspicious links can reduce the risk of exploitation. Until official patches are released, consider restricting access to the vulnerable Lumisxp components or deploying application-layer proxies that sanitize inputs. Additionally, applying Content Security Policy (CSP) headers can help limit the impact of injected scripts by restricting script execution sources. Regularly check for vendor updates and apply patches promptly once available.
Description
A cross-site scripting (XSS) vulnerability in the component XsltResultControllerHtml.jsp of Lumisxp v15.0.x to v16.1.x allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the lumPageID parameter.