Skip to main content
CVE-2025-0619VulnerabilityPublished Updated

CVE-2025-0619: M-Files Server · Insufficiently Protected Credentials

Affects M-Files ServerSource CVE Database V5

0

Not known to be exploited · CVSS 4.6 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
4.6Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:N/VA:N/SC:H/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Jan 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
M-Files Corporation M-Files ServerAffected
  • =0
Fixed in–

AI-suggested

1. Restrict and audit high-privilege accounts on M-Files Server to minimize the number of users who can access sensitive configurations. 2. Implement strict access controls and monitoring on configuration files and password recovery mechanisms within M-Files Server. 3. Use network segmentation and firewall rules to limit access to the M-Files Server management interfaces only to trusted administrators. 4. Regularly review and rotate external connector passwords to reduce the risk window if credentials are exposed. 5. Monitor logs for unusual access patterns or attempts to retrieve configuration data. 6. Engage with M-Files Corporation to obtain and apply security patches or updates as soon as they become available. 7. Consider deploying additional encryption or vaulting solutions for sensitive credentials outside of the M-Files Server configuration. 8. Conduct internal security assessments focusing on privilege escalation and credential exposure risks within the M-Files environment.

Description

Unsafe password recovery from configuration in M-Files Server before 25.1 allows a highly privileged user to recover external connector passwords

References

Community reviews

Loading reviews…