Cross-resource token disclosure via flawed authentication protocol
Published Dec 30, 2022 · Updated Feb 23, 2026
Improper authentication in M-Files Client before 22.5.11356.0 allows remote authenticated users to obtain other users' resource tokens. M-Files identifies the authentication protocol as the affected locus but has not published the incorrect token-validation operation. Exploitation requires server administrator privileges and user interaction; successful use exposes tokens belonging to other users for a different resource.
Summary
What happened
Improper authentication in M-Files Client before 22.5.11356.0 allows remote authenticated users to obtain other users' resource tokens. M-Files identifies the authentication protocol as the affected locus but has not published the incorrect token-validation operation. Exploitation requires server administrator privileges and user interaction; successful use exposes tokens belonging to other users for a different resource.
The record
- CVE
- CVE-2022-4861
- Published
- Dec 30, 2022
- Updated
- Feb 23, 2026
- Vendor
- M-Files
- Product
- M-Files Client
- Classifications
- CWE-303, CWE-287, CAPEC-114, T1528
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Dec 30, 2022CVE publishedPublication date reported by the CVE source.
- Feb 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <22.5.11356.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo