# CVE-2022-1911: Information disclosure in M-Files Server

> Unauthenticated attackers can access underlying operating system information due to a parser error in M-Files Server.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Nov 2022
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-hx75-3jr9-944m

## What is CVE-2022-1911?

CVE-2022-1911 is a medium-severity vulnerability in M-Files Server, published on 30 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Error in parser function in M-Files Server versions before 22.6.11534.1 and before 22.6.11505.0 allowed unauthenticated access to some information of the underlying operating system.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2022-1911?

It affects 1 product.


Products: M-Files M-Files Server.

## How do I fix CVE-2022-1911?

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

## Is CVE-2022-1911 being exploited?

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

## Other vulnerabilities in M-Files Server

- [CVE-2024-10127](https://insights.sbomify.com/CVE-2024-10127/): Support for authentication bypass condition in M-Files LDAP authentication (critical 9.2)
- [CVE-2025-5964](https://insights.sbomify.com/CVE-2025-5964/): Path traversal in M-Files API (high 8.4)
- [CVE-2024-6789](https://insights.sbomify.com/CVE-2024-6789/): Path traversal in M-Files API (high 8.4)
- [CVE-2024-4056](https://insights.sbomify.com/CVE-2024-4056/): Denial of service condition in M-Files Server (high 7.5)
- [CVE-2023-6912](https://insights.sbomify.com/CVE-2023-6912/): Brute force vulnerability in M-Files user authentication (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1911 and fix it if it is affected.

What it is: CVE-2022-1911 is a medium-severity vulnerability in M-Files Server, published on 30 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-1911 in the wild and no public exploit code.

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

## Sources

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

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