Authenticated file disclosure via API path traversal
Published Aug 27, 2024 · Updated Feb 23, 2026
Path traversal in an M-Files Server API endpoint before 24.8.13981.0 allows remote authenticated users to read files from the server. M-Files identifies only an API endpoint and has not disclosed the endpoint, parameter, or precise path-validation failure. A valid account and network access to the API are required; the documented consequence is file disclosure without file modification or service interruption.
Summary
What happened
Path traversal in an M-Files Server API endpoint before 24.8.13981.0 allows remote authenticated users to read files from the server. M-Files identifies only an API endpoint and has not disclosed the endpoint, parameter, or precise path-validation failure. A valid account and network access to the API are required; the documented consequence is file disclosure without file modification or service interruption.
The record
- CVE
- CVE-2024-6789
- Published
- Aug 27, 2024
- Updated
- Feb 23, 2026
- Vendor
- M-Files
- Product
- M-Files Server
- Classifications
- CWE-22, CAPEC-126, T1005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 27, 2024CVE 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 <24.8.13981.0
- Affected versionversion=LTS 23.8.0 <LTS 23.8.12892.0 SR6
- Affected versionversion=LTS 24.2.0 <LTS 24.2.13421.15 SR2
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