Security readout for executives and security teams
Plain-English summary
MISP 2.4.128 allowed a user to access the event contact form path without the expected event-level permission check. This is an access-control defect, not evidence of system takeover. The business concern is unauthorized interaction with event contact workflows in MISP environments.
Executive priority
Handle as a routine but real access-control remediation for MISP operators. Prioritize internet-facing or multi-tenant instances first. There is insufficient source evidence to justify emergency treatment.
Technical view
The CVE states app/Controller/EventsController.php lacked an event ACL check before allowing a user to send an event contact form. The provided sources do not include CVSS, CWE, exploit details, or full impact scope beyond this missing ACL validation.
Likely exposure
Exposure appears limited to organizations running MISP 2.4.128. Risk is higher for multi-user or externally reachable MISP instances where event access boundaries matter. The source bundle does not identify other affected versions.
Exploitation context
The source bundle does not report active exploitation, public exploit availability, or CISA KEV listing. Treat exploitation status as not evidenced, not disproven.
Researcher notes
The key evidence is narrow: missing event ACL validation before sending an event contact form in MISP 2.4.128. No CVSS, CWE, affected-version range, or exploit telemetry is provided, so impact assessment should remain conservative.
Mitigation direction
- Identify any MISP 2.4.128 deployments.
- Review MISP vendor guidance and the referenced upstream commit.
- Upgrade to a vendor-supported release containing the ACL fix.
- Limit MISP access to trusted users and networks where practical.
- Review event contact form usage for unexpected activity.
Validation and detection
- Confirm deployed MISP version on each instance.
- Review EventsController handling for event ACL enforcement.
- Test that unauthorized users cannot send event contact forms.
- Check application logs for unusual contact form submissions.
- Document affected instances and remediation status.
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-2020-15412 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
- CVE List V5 sourceCVE List V5
- https://github.com/MISP/MISP/commit/b0be3b07fee2ab9bf1869ef81a7f24f58bd687efCVE reference · x_refsource_MISC
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.