# CVE-2026-60125: importModule function in MISP ignores per-organisation import module restrictions

> Authenticated users can bypass per-organization restrictions to invoke unauthorized import modules, potentially modifying event data.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2026
- **Updated:** 8 Jul 2026
- **Also known as:** GHSA-6vww-2wx8-q6x4

## What is CVE-2026-60125?

CVE-2026-60125 is a medium-severity missing authorization vulnerability in misp, published on 8 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-60125?


## How do I fix CVE-2026-60125?

No fix has been published for CVE-2026-60125 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-60125 being exploited?

There is no known exploitation of CVE-2026-60125 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-60125 and fix it if it is affected.

What it is: CVE-2026-60125 is a medium-severity missing authorization vulnerability in misp, published on 8 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-60125 in the wild and no public exploit code.

Affected product: misp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-60125/ (Markdown: https://insights.sbomify.com/CVE-2026-60125/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-60125
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-60125
- OSV: https://osv.dev/vulnerability/CVE-2026-60125

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-60125/
Summaries are generated and may contain mistakes; the official description above is the record.