Skip to main content
CVE-2024-29859VulnerabilityPublished Updated

CVE-2024-29859: MISP · n/a

Affects MISPSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 2.4.187 as a priority.

Data as of 26 Oct 2026, 08:30 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Mar 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 misp/MISP to 2.4.187.

Affected software

ProductAffectedFixed in
GitHubmisp/MISPpkg:github/misp/MISPOther threatsAffected
  • <2.4.187
Fixed in
  • 2.4.187

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-29859, organizations should immediately upgrade MISP to version 2.4.187 or later, where the vulnerability is patched. If upgrading is not immediately possible, implement strict network-level access controls to restrict access to the MISP web interface to trusted IP addresses only. Employ web application firewalls (WAFs) with rules to detect and block suspicious file upload attempts targeting the add_misp_export endpoint. Conduct thorough audits of existing uploaded files to detect any unauthorized or malicious content. Disable or restrict file upload functionality if not required for operational needs. Monitor MISP server logs for unusual activity, especially unexpected POST requests to the vulnerable controller. Additionally, enforce secure coding practices and input validation for any custom MISP extensions or integrations. Regularly back up MISP data and configurations to enable recovery in case of compromise. Finally, maintain an incident response plan tailored to MISP compromise scenarios to quickly contain and remediate any exploitation.

Description

In MISP before 2.4.187, add_misp_export in app/Controller/EventsController.php does not properly check for a valid file upload.

References

Community reviews

Loading reviews…