CVE-2025-13008: M-Files Server · Exposure of Private Personal Information to an Unauthorized Actor
Affects M-Files ServerSource CVE Database V5
Not known to be exploited · CVSS 8.6 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% 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:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Dec 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-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| M-Files Corporation M-Files Server | Affected
| Fixed in– |
AI-suggested
Organizations should immediately plan to upgrade M-Files Server to the fixed versions 25.12.15491.7, 25.8 LTS SR3, 25.2 LTS SR3, or 24.8 LTS SR5 once patches are released. In the interim, restrict access to M-Files Web interfaces to trusted networks and users only, and enforce strong authentication mechanisms such as multi-factor authentication to reduce the risk of attacker authentication. Monitor active sessions for unusual activity and consider implementing session timeout policies to limit token validity periods. Employ network segmentation and web application firewalls to detect and block suspicious requests targeting session management endpoints. Educate users about phishing and social engineering risks that could facilitate attacker authentication. Review and harden session management configurations, including secure cookie flags (HttpOnly, Secure, SameSite) and token storage practices. Conduct regular audits of user sessions and logs to identify potential token theft attempts. Finally, maintain an incident response plan to quickly address any detected compromise related to session hijacking.
Description
An information disclosure vulnerability in M-Files Server before versions 25.12.15491.7, 25.8 LTS SR3, 25.2 LTS SR3 and 24.8 LTS SR5 allows an authenticated attacker using M-Files Web to capture session tokens of other active users.