Security readout for executives and security teams
Plain-English summary
MISP versions before 2.4.148 contain a command injection flaw in an Open Data export component. If reachable by an attacker, mishandled input could influence a server-side shell execution path. The sources do not provide CVSS, affected CPEs, or confirmed exploitation evidence.
Executive priority
Prioritize remediation for any supported MISP deployment below 2.4.148. Command injection can affect server integrity, but the available evidence does not prove active exploitation or define internet exposure.
Technical view
The vulnerable path is app/Lib/Export/OpendataExport.php. Parameter data is mishandled before use in a shell_exec call, creating command injection risk. Public references identify the fix in MISP 2.4.148 via commit e36f73947e741bc97320f0c42199acd1a94c7051 and the v2.4.147 to v2.4.148 comparison.
Likely exposure
Exposure is likely limited to organizations running MISP before 2.4.148, especially where Open Data export functionality is accessible. The bundle does not specify required privileges, affected CPEs, or deployment conditions.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not listed as KEV in the bundle. Treat this as a serious command injection risk, but avoid assuming exploitation without local evidence.
Researcher notes
The public record is sparse: no CVSS, CWE, CPEs, or privilege requirements are included in the bundle. Analysis should focus on the shell_exec data flow in OpendataExport.php and the exact changes in the 2.4.148 fix.
Mitigation direction
- Upgrade MISP to version 2.4.148 or later.
- Review the referenced MISP fixing commit and release comparison.
- Restrict access to export functionality until upgraded.
- Check MISP vendor guidance for any additional hardening steps.
Validation and detection
- Inventory all MISP instances and record exact versions.
- Confirm no production instance is older than 2.4.148.
- Verify the vulnerable OpendataExport.php path is patched or absent.
- Review application and system logs for unusual export activity.
- Document whether export access requires authentication in your deployment.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CVE-2021-41326 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.