CVE-2023-47268: In libslic3r/GCode/PostProcessor.cpp in Prusa PrusaSlicer through 2.6.1, a crafted 3mf project file can exe...
In libslic3r/GCode/PostProcessor.cpp in Prusa PrusaSlicer through 2.6.1, a crafted 3mf project file can execute arbitrary code on a host where the project is sliced and G-code exported.
Security readout for executives and security teams
Plain-English summary
CVE-2023-47268 affects PrusaSlicer through 2.6.1. A malicious 3MF project file can run code on a user’s computer when the file is sliced and G-code is exported. Business risk is highest where staff download, share, or process untrusted 3D printing projects.
Executive priority
Prioritize remediation for teams that process external 3D printing files. This is not evidenced as actively exploited, but it can turn a normal design-file workflow into workstation code execution. Treat it as a targeted workstation risk rather than an internet-scale emergency.
Technical view
The CVE describes arbitrary code execution in libslic3r/GCode/PostProcessor.cpp via crafted 3MF project files. The issue is classified as CWE-77 and has CVSS 5.3 because exploitation is local and requires user interaction, but no privileges. Impact includes limited confidentiality, integrity, and availability compromise on the slicing host.
Likely exposure
Organizations using PrusaSlicer through 2.6.1 are potentially exposed, especially shared workstations, makerspaces, labs, engineering teams, and print farms handling third-party 3MF files. Exposure is lower where only trusted project files are opened and exported.
Exploitation context
The CVE is not listed in CISA KEV, and the supplied sources do not show active exploitation. A public exploit-oriented archive is referenced, so treat untrusted 3MF files as potentially dangerous, but do not assume widespread exploitation from the provided evidence.
Researcher notes
The source bundle names PrusaSlicer through 2.6.1 but does not include a detailed vendor advisory or explicit fixed version. Analysis should focus on 3MF project handling, post-processing script behavior, and user-driven export workflows. Avoid claiming active exploitation without additional evidence.
Mitigation direction
Avoid opening or exporting untrusted 3MF project files in affected PrusaSlicer versions.
Check Prusa guidance and downloads for fixed or current versions.
Run slicer workstations with least privilege, not administrator accounts.
Use isolated machines or sandboxes for third-party 3D model processing.
Review project and application settings for unexpected post-processing scripts.
Validation and detection
Inventory PrusaSlicer installations and identify versions through 2.6.1.
Confirm whether users process externally sourced 3MF project files.
Inspect slicer configurations for post-processing script usage.
Review endpoint alerts around slicer execution and child process creation.
Verify remediation against current Prusa documentation or release downloads.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-77: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-77 · source CWE mapping
Improper Neutralization of Special Elements used in a Command ('Command Injection')
Improper Neutralization of Special Elements used in a Command ('Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.