CVE-2024-54675: MISP · Cross-site Scripting
Affects MISPSource CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 26 Oct 2026, 11:42 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% 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 4 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubmisp/MISPpkg:github/misp/MISPOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until an official patch is released, organizations should implement several specific mitigations to reduce risk from CVE-2024-54675. First, restrict access to the MISP workflows editor interface to trusted users only, using network segmentation, VPNs, or IP whitelisting to limit exposure. Second, enforce strict input validation and sanitization on all user inputs in the workflows editor, if possible via custom configurations or temporary code modifications, to prevent malicious script injection. Third, educate users to be cautious when interacting with ad-hoc workflows, especially those created by untrusted sources, and to report suspicious behavior. Fourth, enable Content Security Policy (CSP) headers on the MISP web server to restrict execution of inline scripts and loading of untrusted resources, mitigating the impact of injected scripts. Fifth, monitor logs and user activity for unusual patterns that may indicate exploitation attempts. Finally, stay updated with MISP vendor announcements and apply patches promptly once available. If feasible, consider deploying web application firewalls (WAFs) with rules targeting XSS payloads in the workflows editor endpoints to provide an additional layer of defense.
Description
app/webroot/js/workflows-editor/workflows-editor.js in MISP through 2.5.2 has stored XSS in the editor interface for an ad-hoc workflow.