dbcve.org
M Files ServerApplication · M Files

CVE-2025-5964

MEDIUM · 6.5 CVSS v3.1 Published 2025-06-15
Fix available
A fix is available. Upgrade to 24.8.13981.16 / 25.2.14524.9 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A path traversal vulnerability in M-Files Server's API endpoint allows authenticated users to access arbitrary files on the server file system by manipulating path references in API requests.

MitigationUpgrade to M-Files Server version 25.6.14925.0 or later to obtain the security patch.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
M Files ServerApplication
Affected:< 24.8.13981.16>= 25.2.14524.3, < 25.2.14524.9>= 25.3.14681.7, < 25.6.14925.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed M-Files Server version
    Open M-Files Admin, navigate to the server node, and locate the version information in the general settings. Alternatively, check the Windows Programs and Features list for M-Files Server version, or use PowerShell with the M-Files admin module if available.
    Affected if The installed version falls within any of these ranges: < 24.8.13981.16; >= 25.2.14524.3 and < 25.2.14524.9; >= 25.3.14681.7 and < 25.6.14925.0
  2. Confirm M-Files API endpoint is enabled
    In M-Files Admin, navigate to Server | XML Web Services or API settings to verify the REST API or XML Web Services endpoint is enabled. If using IIS, check the M-Files Web Service application is running.
    Affected if The API endpoint is enabled and accessible over the network.
  3. Verify M-Files authentication configuration
    In M-Files Admin under Authentication Methods, confirm that user authentication is configured and active. The vulnerability requires an authenticated user session to exploit the path traversal.
    Affected if Authentication is enabled and users can log in to the M-Files system.

You are affected if your M-Files Server version is within the vulnerable ranges AND the API endpoint is enabled with authentication available to users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 24.8.13981.16 / 25.2.14524.9 / 25.6.14925.0 or later
Fixed in 24.8.13981.1625.2.14524.925.6.14925.0
Interim mitigation

Upgrade to M-Files Server version 25.6.14925.0 or later to obtain the security patch.

Recommended fix High confidence

25.6.14925.0

  1. 1. Identify the current M-Files Server version by checking the About section in M-Files admin or via the server's version information
  2. 2. Plan and schedule a maintenance window for the upgrade, ensuring proper backup procedures are in place
  3. 3. Back up the M-Files database and server configuration before proceeding with the upgrade
  4. 4. Download M-Files Server version 25.6.14925.0 or later from the vendor's official download portal (empower.m-files.com or product.m-files.com)
  5. 5. Install the upgrade following M-Files official upgrade documentation for your specific version path
  6. 6. After installation, verify the server is running and accessible
  7. 7. Confirm the fix by checking that the API endpoint no longer allows path traversal attacks
  8. 8. Review M-Files release notes for version 25.6.14925.0 to ensure all environment requirements are met

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in M Files Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5964 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-5964 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data