CVE-2025-30075 In Alludo MindManager before 25.0.208 on Windows, attackers could potentially execute code as other local users on the same machine if they
Low 2.2
Published
Updated
Check this codebase for CVE-2025-30075 and fix it if it is affected.
What it is: CVE-2025-30075 is a low-severity vulnerability in Alludo MindManager, published on 16 Sep 2025.
Exploitation: There is no known exploitation of CVE-2025-30075 in the wild and no public exploit code.
Affected product: Alludo MindManager. 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-2025-30075/ (Markdown: https://insights.sbomify.com/CVE-2025-30075/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2025-30075?
CVE-2025-30075 is a low-severity vulnerability in Alludo MindManager, published on 16 Sep 2025.
Official description
In Alludo MindManager before 25.0.208 on Windows, attackers could potentially execute code as other local users on the same machine if they could write DLL files to directories within victims' DLL search paths.
Weakness: CWE-673
Which versions are affected by CVE-2025-30075?
How do I fix CVE-2025-30075?
No fix has been published for CVE-2025-30075 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-30075 being exploited?
There is no known exploitation of CVE-2025-30075 in the wild and no public exploit code.
Sources
Also known as GHSA-8rrr-f7fx-j768.