Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with editor rights on one event
-
DeliveryObtain valid foreign report UUID
-
ExploitCreate/edit report supplying that UUID
-
ExecutioneditReport adopts report lacking event check
-
PersistReport reparented into attacker's event
-
ImpactRead and overwrite private cross-event report
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Exploitation requires an authenticated MISP account holding editor (write) rights on at least one event (PR:L) and knowledge or a valid guess of the target report's UUID - a high-entropy identifier that limits blind or automated abuse. The flaw is reached through the normal report create/edit (and populate/pull) code path in EventReport::editReport() on MISP instances before 2.5.47 where reports from other events exist and are shared or restricted. Limiting factors: the attacker cannot enumerate UUIDs and must obtain them out-of-band; impact is confined to event report objects rather than the full MISP dataset; and instances with only a single event or a single trusted user have negligible exposure. There is no user-interaction requirement on the victim (UI:N). |
| Impact | This is a genuine but bounded authorization flaw (CWE-639 IDOR), not a high-CVSS-low-risk artifact nor a top-tier emergency. The vendor CVSS 4.0 score of 6.4 (AV:N/AC:L/AT:N/PR:L/UI:N with vulnerable-system impacts VC:N/VI:N/VA:N but subsequent-system SC:H/SI:H) reflects a deliberate modeling choice: the attacker's own event is the 'vulnerable system' (no impact) and the victim's event is a 'subsequent system' that suffers high confidentiality and integrity loss - i.e., MISP treats the cross-event boundary as a scope change. That is defensible but unusual; a more conventional CVSS 3.1 reading places the impact directly on confidentiality/integrity of report data. No EPSS score, KEV listing, POC, or SSVC decision data was provided, so exploitation-likelihood signals are absent; there is no public exploit identified at time of analysis. The realistic risk is driven by two gating factors baked into the vector: PR:L (the attacker must already hold editor rights on at least one event) and knowledge/guessing of a valid report UUID. UUIDs are high-entropy and not enumerable, so blind cross-event theft is impractical - the plausible attacker is an existing authenticated MISP user who has learned a target report's UUID (e.g., via sharing, logs, or a prior compromise). Net: a medium-severity insider/collaborator authorization-boundary bypass, worth patching to 2.5.47 in multi-tenant or broadly-shared MISP instances, but not an unauthenticated internet-facing crisis. |
| Exploit ScenarioDerived | An authenticated MISP user with editor rights on their own event learns or discovers the UUID of a private report belonging to another (restricted) event. They create or edit a report in their own event and supply that UUID; because editReport() locates the existing report by UUID without confirming it belongs to the current event, the foreign report is reparented into the attacker's event, where they can now view and overwrite its previously restricted contents. No public exploit code was provided in the intelligence, and exploitation requires prior editor access plus a valid target UUID. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 21, 2026
Authenticated users with editor (write) rights on at least one event in MISP can reparent an event report belonging to a different event by supplying that report's UUID during report creation or editing, because EventReport::editReport() matched existing rows by UUID without verifying the report's event_id matched the target event. Successful exploitation lets the attacker read and modify private reports they were never authorized to access, though impact is confined to report objects rather than the full instance dataset and the attacker must already know or guess the high-entropy UUID - a barrier that prevents enumeration or automated abuse. Affected versions are MISP before 2.5.47; no public exploit code or confirmed active exploitation was identified at time of analysis.
RemediationAI
Upgrade to MISP 2.5.47 or later, which contains the event_id ownership check added in upstream commit 43665b9bb (https://github.com/MISP/MISP/commit/43665b9bb); this is the only complete fix, since the patch enforces that a report found by UUID must already belong to the event being edited. If immediate upgrade is not possible, compensating controls are: temporarily strip editor/write rights from users who do not strictly need them, since exploitation requires PR:L on at least one event - the trade-off is reduced analyst throughput for report contributions; and, where federation or sync-populate flows are not essential, pause those pull/populate jobs, as the vulnerable code path is also reachable through nested event edit/populate handling. Because the attacker must already possess or guess a valid report UUID, review MISP logs and audit event_reports rows for records whose event_id does not match the event they appear under, and for cross-event report move/reparent activity around suspicious accounts - this detects abuse but does not prevent it. Limit report sharing distributions so fewer UUIDs are discoverable by non-owning users, accepting the cost of reduced cross-team intelligence sharing. Note that no vendor-released patch was superseded and no workaround fully restores the missing authorization check; these measures only reduce attack surface until the 2.5.47 upgrade is applied.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This is an authorization bypass through a user-controlled key (CWE-639 / IDOR) in MISP, the Malware Information Sharing Platform, a PHP/CakePHP threat-intelligence application backed by MySQL. MISP event reports are first-class records (EventReport model) linked to a parent event via event_id, and each report carries a globally unique UUID - the identifier used by the internal sync/pull logic to decide whether an incoming report is new or already exists. In app/Model/EventReport.php::editReport(), the lookup of an existing report by UUID did not constrain the result to the event currently being edited, so the subsequent save path could 'adopt' and rewrite a row whose real parent was a different event. The vendor fix (commit 43665b9bb) adds an explicit comparison of the found row's event_id against the eventId under which the edit is occurring and returns the error 'Event Report %s already belongs to a different event.' rather than reparenting it; the commit notes that legitimate sync re-captures a report under the same event, so only true cross-event collisions are rejected. The flaw is reachable through normal report create/edit paths and nested event edit, populate, or pull flows, and applies to all MISP CPE variants (cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*) prior to 2.5.47. The CVSS 4.0 vector rates subsequent-system confidentiality and integrity as High (SC:H/SI:H) while the vulnerable system itself shows no direct C/I/A impact; the independent assessment lands on CVSS:3.1 6.4-equivalent severity with PR:L and UI:N, meaning the attacker must be an authenticated editor but no action is required from the victim.
Know when Misp gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N
Network-exposed authenticated web app so AV:N/AC:L/PR:L; foreign report content is disclosed (C:L, bounded to report data) and overwritten (I:H); no availability impact and scope kept unchanged within one application authority.
Primary rating from Vendor (CIRCL).
CVSS VectorVendor: CIRCL
DescriptionCVE.org
When a user creates or edits a report inside an event, MISP can identify an existing report using its UUID without properly checking whether that report actually belongs to the same event.
As a result, a user who has editing rights on one event could potentially move a report from another event into their own event, as long as they know or can guess the report’s UUID. Once moved, they could view and change information that they were not originally allowed to access.
The vulnerability requires the attacker to have editor access to at least one event and to know or discover a valid report UUID.
The main impact is that private event reports could be exposed or modified across event boundaries, bypassing MISP’s normal access restrictions.
Version affected: <2.5.47
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
An issue was discovered in MISP 2.4.9x before 2.4.99. Rated high severity (CVSS 8.8), this vulnerability is remotely exp
An issue was discovered in MISP before 2.4.158. Rated critical severity (CVSS 9.8), this vulnerability is remotely explo
app/Controller/Component/IndexFilterComponent.php in MISP before 2.4.167 mishandles ordered_url_params and additional_de
SQL injection in MISP threat intelligence platform versions prior to 2.5.37 allows remote unauthenticated attackers to m
An issue was discovered in MISP before 2.4.158. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitab
MISP 2.4.172 mishandles different certificate file extensions in server sync. Rated high severity (CVSS 7.5), this vulne
In MISP before 2.4.148, app/Lib/Export/OpendataExport.php mishandles parameter data that is used in a shell_exec call. R
An issue was discovered in app/Controller/UsersController.php in MISP 2.4.92. Rated critical severity (CVSS 9.8), this v
An issue was discovered in MISP 2.4.128. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable,
MISP before 2.4.135 lacks an ACL check, related to app/Controller/GalaxyElementsController.php and app/Model/GalaxyEleme
app/View/Elements/genericElements/IndexTable/Fields/generic_field.ctp in MISP 2.4.144 does not sanitize certain data rel
MISP 2.4.148, in certain configurations, allows SQL injection via the app/Model/Log.php $conditions['org'] value. Rated
EUVD-2026-83911
GHSA-rq8q-gvp5-cmqp
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB