M-Files Server up to 22.3.11237.1 Token incorrect implementation of authentication algorithm
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in M-Files Server. This vulnerability affects unknown code of the component Token Handler. Executing a manipulation can lead to incorrect implementation of authentication algorithm. This vulnerability is handled as CVE-2022-4861. The attack can be executed remotely. There is not any exploit available. The affected component should be upgraded.
Details
A vulnerability has been found in M-Files Server and classified as problematic. This vulnerability affects an unknown part of the component Token Handler. The manipulation with an unknown input leads to a incorrect implementation of authentication algorithm vulnerability. The CWE definition for the vulnerability is CWE-303. The requirements for the product dictate the use of an established authentication algorithm, but the implementation of the algorithm is incorrect. As an impact it is known to affect confidentiality. CVE summarizes:
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.
The weakness was released 12/30/2022. The advisory is available at m-files.com. This vulnerability was named CVE-2022-4861 since 12/30/2022. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available.
Upgrading to version 22.5.11356.0 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.9VulDB Meta Temp Score: 3.9
VulDB Base Score: 2.0
VulDB Temp Score: 1.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.9
NVD Vector: 🔍
CNA Base Score: 4.8
CNA Vector (M-Files Corporation): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Incorrect implementation of authentication algorithmCWE: CWE-303
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Server 22.5.11356.0
Timeline
12/30/2022 🔍12/30/2022 🔍
12/30/2022 🔍
02/23/2026 🔍
Sources
Advisory: m-files.comStatus: Confirmed
CVE: CVE-2022-4861 (🔍)
GCVE (CVE): GCVE-0-2022-4861
GCVE (VulDB): GCVE-100-217066
Entry
Created: 12/30/2022 17:22Updated: 02/23/2026 12:23
Changes: 12/30/2022 17:22 (48), 01/26/2023 10:01 (11), 08/28/2024 15:04 (17), 04/28/2025 09:59 (3), 02/23/2026 12:23 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.