# CVE-2024-11176: Incorrect evaluation of effective permissions in M-Files Aino

> An authenticated user can access unauthorized object information due to incorrect permission evaluation in M-Files Aino.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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:** 20 Nov 2024
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-fwqv-682v-f9jf

## What is CVE-2024-11176?

CVE-2024-11176 is a medium-severity missing authorization vulnerability in M-Files Aino, published on 20 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper access control vulnerability in M-Files Aino in versions before 24.10 allowed an authenticated user to access object information via incorrect evaluation of effective permissions.

Weakness: CWE-863 (Incorrect Authorization), CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2024-11176?


## How do I fix CVE-2024-11176?

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

## Is CVE-2024-11176 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-11176 and fix it if it is affected.

What it is: CVE-2024-11176 is a medium-severity missing authorization vulnerability in M-Files Aino, published on 20 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-11176 in the wild and no public exploit code.

Affected product: M-Files Aino. 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-2024-11176/ (Markdown: https://insights.sbomify.com/CVE-2024-11176/index.md)
```

## Sources

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

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