Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Any authenticated MISP user (PR:L) can reach the endpoints over the network with no UI; ownership hijack lets one org affect another org's data, so scope-change with high confidentiality and integrity impact and no availability impact.
Primary rating from Vendor (5a6e4751-2f3f-4070-9419-94fb35b644e8).
CVSS VectorVendor: 5a6e4751-2f3f-4070-9419-94fb35b644e8
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Lifecycle Timeline
3DescriptionCVE.org
MISP contained multiple mass assignment vulnerabilities in the handling of collections, tag collections, event delegations, and shadow attributes. Several controller actions accepted user-supplied fields that should have remained server-controlled, including record identifiers and ownership-related fields such as id, org_id, orgc_id, and user_id.
An authenticated attacker with access to the affected endpoints could craft requests containing protected fields in order to alter object ownership, redirect an update to another record, overwrite existing event delegation requests, or modify shadow attribute proposals belonging to another organization. This could result in unauthorized modification of MISP objects and, depending on object visibility and sharing configuration, unauthorized access to or transfer of sensitive threat intelligence data.
The issue was fixed by explicitly pinning ownership and identity fields to their stored values during edit operations and by removing user-supplied primary keys from create-only save paths.
Affected components:
- CollectionsController::edit()
- EventDelegationsController::delegateEvent()
- ShadowAttributesController::edit()
- TagCollectionsController::edit()915
- TagCollectionsController::editWithTags()
Attack requirements: The attacker must be authenticated and able to reach the affected MISP endpoints. No user interaction is required.
AnalysisAI
Mass assignment flaws in MISP (Malware Information Sharing Platform) let authenticated users overwrite server-controlled fields such as id, org_id, orgc_id, and user_id when submitting requests to several edit endpoints, enabling ownership transfer, hijacking of arbitrary collection/delegation/proposal records, and unauthorized access to threat-intelligence objects belonging to other organizations. No public exploit identified at time of analysis, and the issue is not in CISA KEV; the underlying CWE-639 weakness is addressed by upstream commit 9341690.
Technical ContextAI
MISP is a PHP/CakePHP threat-intelligence sharing platform. The affected controllers (CollectionsController, EventDelegationsController, ShadowAttributesController, TagCollectionsController) rely on a generic CRUDComponent::edit() helper that copies every supplied request field onto the loaded model, and on Collection::beforeValidate() which only pins ownership on create (when id is empty). This is a classic CWE-639 'Authorization Bypass Through User-Controlled Key' / mass-assignment pattern: route-level auth (mayModify) only validated the URL id, while the request body could carry additional primary-key and ownership fields that the ORM happily persisted, turning an edit() call into either a record-redirect or an ownership reassignment.
RemediationAI
Upstream fix available (commit 9341690e9b6dde7f0605edea5533e05ba7362e35) - released patched version not independently confirmed, so administrators should update to the next MISP release that ships this commit or cherry-pick it directly from https://github.com/MISP/MISP/commit/9341690e9b6dde7f0605edea5533e05ba7362e35. As a compensating control until the patch is deployed, restrict the affected endpoints (collections/edit, eventDelegations/delegateEvent, shadow_attributes/edit, tag_collections/edit and editWithTags) at the reverse proxy to trusted org-admin source IPs or temporarily disable collections, tag collections, and event delegation features for non-trusted users - accepting the side effect that legitimate cross-org delegation and collaborative tagging workflows will break. Reviewing audit logs for unexpected changes to org_id/orgc_id/user_id on Collection, TagCollection, EventDelegation, and ShadowAttribute records is recommended to detect prior abuse.
Same technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-36554
GHSA-94hj-x7j9-542x