Vulnerability Description
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.
Related Weaknesses (CWE)
References
FAQ
What is CVE-2026-60125?
CVE-2026-60125 is a documented vulnerability. 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...
How severe is CVE-2026-60125?
CVSS scoring is not yet available for CVE-2026-60125. Check NVD for updates.
Is there a patch for CVE-2026-60125?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.