CVE-2025-5964: M-Files Server · Path Traversal
Affects M-Files ServerSource CVE Database V5
Not known to be exploited · 13% EPSS · CVSS 8.4 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 13.0% chance of exploitation in 30 days – higher than 96% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:N/RE:M/U:GreenExploitation evidence
Disclosed: evidence found.
CVE published 15 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| M-Files Corporation M-Files Server | Affected
| Fixed in– |
AI-suggested
1. Immediately monitor for updates and patches from M-Files Corporation and apply the official patch for version 25.6.14925.0 or later as soon as it is released. 2. Restrict access to the M-Files Server API endpoints to only trusted and necessary users and systems using network segmentation and firewall rules. 3. Enforce strong authentication mechanisms, including multi-factor authentication (MFA), to reduce the risk of compromised credentials being used to exploit this vulnerability. 4. Conduct regular audits of user accounts and permissions to ensure that only authorized personnel have access to the server and its API. 5. Implement application-layer filtering or web application firewalls (WAFs) that can detect and block path traversal patterns in API requests. 6. Monitor server logs for unusual file access patterns or attempts to access files outside expected directories. 7. Educate administrators and users about the risks of credential compromise and the importance of secure password practices. 8. If patching is delayed, consider temporarily disabling or restricting the vulnerable API endpoints if feasible without disrupting business operations. 9. Review and harden file system permissions on the server to minimize the exposure of sensitive files even if path traversal is attempted.
Description
A path traversal issue in the API endpoint in M-Files Server before version 25.6.14925.0 allows an authenticated user to read files in the server.