Skip to main content
VulnerabilityPublished Updated

CVE-2024-56082: Lumos · Cross-site Scripting

Affects LumosSource CVE Database V5

0

Not known to be exploited · CVSS 3.5 Low : upgrade to 1.0.17 when convenient.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
3.5Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.0.17
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Dec 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

Upgrade andrewnguonly/Lumos to 1.0.17.

Affected software

ProductAffectedFixed in
GitHubandrewnguonly/Lumospkg:github/andrewnguonly/LumosOther threatsAffected
  • <1.0.17
Fixed in
  • 1.0.17

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-56082, organizations should upgrade Lumos to version 1.0.17 or later, where the markdown-to-jsx package is properly configured to disable raw HTML parsing. If upgrading is not immediately possible, a temporary mitigation is to manually configure the markdown-to-jsx renderer to set disableParsingRawHTML to true, preventing raw HTML from being parsed and rendered. Additionally, implement Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of potential XSS attacks. Input validation and sanitization should be enforced on all user-submitted Markdown content to strip or encode potentially dangerous HTML tags and attributes. Regularly audit and monitor application logs for suspicious activity related to Markdown input processing. Educate users about the risks of interacting with untrusted content and encourage cautious behavior when clicking links or executing scripts within the application. Finally, conduct security testing focused on Markdown rendering components to identify and remediate similar issues proactively.

Description

ChatBar.tsx in Lumos before 1.0.17 parses raw HTML in Markdown because the markdown-to-jsx package is used without disableParsingRawHTML set to true.

References

Community reviews

Loading reviews…