MISP contains an authorization bypass vulnerability in the SharingGroup model's captureSGExisting method. This flaw allows users with the sync permission to bypass membership checks and gain unauthorized read access to restricted sharing groups. Exploitation requires an authenticated sync user who knows a valid sharing group UUID. The attacker can modify sharing group records to add their organization as a member, exposing sensitive threat intelligence data. The vulnerability affects MISP versions up to 2.5.51 and has a medium severity rating.
MISP versions prior to 2.5.48 have a vulnerability in the handling of module plugin settings where sensitive flags such as redacted and cli_only are dropped during server processing. This causes sensitive information like API keys to be exposed to any authenticated user with access to server settings, and allows modification of settings intended to be restricted to CLI-only access.
MISP versions prior to 2.5.48 contain a vulnerability in the server settings lookup mechanism that allows authenticated users to retrieve sensitive configuration data that should have been redacted. This occurs because branch nodes in the configuration tree do not carry redaction flags, enabling full branch contents—including security salts, Redis passwords, and plugin API keys—to be exposed. The vulnerability affects endpoints that retrieve and edit server settings, leading to unauthorized disclosure of sensitive server secrets.
MISP versions prior to 2.5.48 contain a reflected cross-site scripting (XSS) vulnerability in the workflow module interface. This flaw arises because parameter names returned by the misp-modules service are rendered as raw HTML without proper output encoding. An attacker who can influence these parameter names may inject arbitrary JavaScript that executes in the context of an authenticated user's browser, potentially leading to session token theft or unauthorized actions.
MISP versions prior to 2.5.48 contain a CSS injection vulnerability in the remote event preview feature. This occurs because the colour value of remote tags is inserted directly into an inline CSS style attribute without sufficient validation. An attacker controlling a linked MISP server can inject arbitrary CSS by crafting malicious tag colour values, which are then rendered when a user previews events from that linked server. This can lead to UI manipulation, visual spoofing, or limited information disclosure via CSS techniques.
MISP versions up to 2.5.48 contain a data integrity vulnerability in the event deletion process. When an event is deleted by an authenticated user with sufficient privileges, several associated records such as report tags, graph entries, correlations, ssdeep chunks, and attachment scan results are not removed, resulting in orphaned database entries. These residual records may retain sensitive threat intelligence data and could be exposed through other application queries or administrative interfaces. This flaw leads to unintended data retention and potential information exposure, as well as possible storage bloat over time.
A logic error in MISP event synchronization caused non-exportable tags to be improperly filtered, leading to exposure of sensitive tag information to remote instances during event pushes. This affects MISP versions prior to 2.5.48 when pushing multiple reports in a synchronization. Additionally, pushing an empty last report could cause the remote instance to fail saving the event.
MISP versions prior to 2.5.48 contain an access control vulnerability in the proposal visibility logic. Users in a sharing group could view proposed changes to attributes or objects associated with that group regardless of the intended distribution level restrictions. Additionally, the owning organisation could not view proposals on its own organisation-only attributes. This flaw leads to unauthorized disclosure of proposed attribute changes.