CVE-2024-51330: Cura · Code Injection
Affects CuraSource CVE Database V5
Not known to be exploited · CVSS 4.4 Medium.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Nov 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 |
|---|---|---|
GitHubultimaker/Curapkg:github/ultimaker/CuraOther 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
To mitigate CVE-2024-51330, organizations should first restrict local access to systems running vulnerable versions of UltiMaker Cura, ensuring only trusted users have high-level privileges. Implement strict endpoint security controls, including application whitelisting and behavior monitoring, to detect unauthorized code execution attempts. Network segmentation should isolate 3D printing workstations from general user environments to reduce exposure. Regularly audit user permissions and remove unnecessary administrative rights. Until a patch is released, consider using alternative 3D printing management software or upgrading to versions confirmed to be unaffected. Additionally, monitor vendor communications for updates or patches addressing this vulnerability. Employing host-based intrusion detection systems (HIDS) can help identify suspicious IPC activity between Cura components. Finally, educate users about the risks of local privilege escalation and enforce strong authentication and access policies to minimize insider threats.
Description
An issue in UltiMaker Cura v.4.41 and 5.8.1 and before allows a local attacker to execute arbitrary code via Inter-process communication (IPC) mechanism between Cura application and CuraEngine processes, localhost network stack, printing settings and G-code processing and transmission components, Ultimaker 3D Printers.