CVE-2026-60125: importModule function in MISP ignores per-organisation import module restrictions
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-60125?
The severity of CVE-2026-60125 is medium with a CVSS score of 5.3.
How do I fix CVE-2026-60125?
To fix CVE-2026-60125, ensure that the importModule function correctly enforces per-organisation import module restrictions during module lookups.
What software is affected by CVE-2026-60125?
The software affected by CVE-2026-60125 is MISP.
What type of vulnerability is CVE-2026-60125?
CVE-2026-60125 is a vulnerability related to improper enforcement of module restrictions within the MISP platform.
Who is impacted by CVE-2026-60125?
Authenticated users from organizations that are restricted from using certain modules may be impacted by CVE-2026-60125.