CVE-2026-60125
MediumCVSS 5.3Exploitation Probability (EPSS)
Low risk11th percentile - higher than 11% of all known CVEs
Summary
In MISP, the importModule() function used getEnabledModule() to resolve import modules by name but did not enforce per-organization restrictions. An authenticated user from a restricted organization could still invoke the module directly if they knew its name.
Risk Assessment
The risk is unauthorized access to restricted import-module functionality, potentially allowing unauthorized import or modification of event data based on the module and user permissions.
Recommendation
Immediately update MISP to a version that fixes the enforcement of organization restrictions in the importModule() function.
Other vulnerabilities in MISP
See all- CVE-2026-61474Medium
An improper authorization check in MISP's attribute creation endpoint allowed an authenticated user with permission to add attributes to submit a sharing_group_id without triggering the corresponding sharing group authorization check, as long as the attribute distribution value was not explicitly set to 4 — 'sharing group'.
- CVE-2017-14337High
In MISP versions before 2.4.80, when configured with X.509 certificate authentication alongside a non-MISP external user management API, an unauthenticated user can gain access as an arbitrary user if the API returns an empty value.
- CVE-2026-10868Critical
MISP has a mass assignment vulnerability in the user edit functionality (UsersController::edit()). An authenticated attacker can modify the user ID in the request, leading to updates on another user's account.
- CVE-2026-10611Critical
MISP contains an authentication bypass vulnerability when LDAP mixed authentication is enabled with OTP enforcement. An authenticated user can bypass the OTP step and access the application without providing a TOTP, HOTP, or email OTP code.
- CVE-2024-29859Critical
In MISP before version 2.4.187, the add_misp_export function in app/Controller/EventsController.php does not properly check for a valid file upload.
- CVE-2024-25674Critical
An issue was discovered in MISP before version 2.4.184 related to insecure organization logo uploads due to a lack of checks for file extension and MIME type.
- CVE-2023-50918Critical
In app/Controller/AuditLogsController.php in MISP before version 2.4.182, ACLs for audit logs are mishandled.
- CVE-2023-48659Critical
An issue was discovered in MISP before version 2.4.176 related to mishandling parameter parsing in app/Controller/AppController.php.
- CVE-2022-29528Critical
An issue was discovered in MISP before version 2.4.158 related to PHAR deserialization.
- CVE-2021-39302Critical
MISP version 2.4.148, in certain configurations, allows SQL injection via the $conditions['org'] value in the app/Model/Log.php file.
Original NVD description (English source)
MISP’s importModule() path used getEnabledModule() to resolve a single import module by name, but this lookup did not enforce the per-organisation module restriction checked by getEnabledModules(). As a result, an authenticated user from an organisation that was not allowed to use a module restricted via Plugin.Import_<module>_restrict could still invoke that import module directly if they knew its name. This could allow unauthorised access to restricted import-module functionality and, depending on the module and the user’s event permissions, may allow unauthorised import or modification of event data through a module that should have been unavailable to the user’s organisation.