Token disclosure via configuration-dependent sensitive logging
Published Dec 30, 2022 · Updated Feb 23, 2026
Sensitive-data logging in M-Files Server before 22.10.11846.0 allows local users to obtain sensitive tokens from stored logs. Under specific configurations, the server writes sensitive tokens to log files that are expected not to contain them; M-Files has not identified the responsible component or setting. Access to the server or other log storage is required, and a role able to read those files can recover tokens without altering data or interrupting service.
Summary
What happened
Sensitive-data logging in M-Files Server before 22.10.11846.0 allows local users to obtain sensitive tokens from stored logs. Under specific configurations, the server writes sensitive tokens to log files that are expected not to contain them; M-Files has not identified the responsible component or setting. Access to the server or other log storage is required, and a role able to read those files can recover tokens without altering data or interrupting service.
The record
- CVE
- CVE-2022-4858
- Published
- Dec 30, 2022
- Updated
- Feb 23, 2026
- Vendor
- M-Files
- Product
- M-Files Server
- Classifications
- CWE-532, CAPEC-545, T1552.001
- Attack vector
- local
- 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.10.11846.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