dbcve.org
M Files ServerApplication · M Files

CVE-2024-6789

MEDIUM · 6.5 CVSS v3.1 Published 2024-08-27
Fix available
A fix is available. Upgrade to 24.2.13421.15 / 24.8.13981.0 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 API endpoint in M-Files Server before version 24.8.13981.0 and LTS 24.2.13421.15 SR2 and LTS 23.8.12892.0 SR6 allows authenticated user to read files

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 · high confidence

A path traversal vulnerability in M-Files Server API endpoint allows authenticated users to read arbitrary files on the system by manipulating file paths in API requests. This occurs due to insufficient input validation in the file access functionality.

MitigationUpdate M-Files Server to version 24.8.13981.0 or later, or apply the relevant LTS SR2/SR6 patches for LTS 24.2 and LTS 23.8 releases.

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.2.13421.15< 24.8.13981.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. Identify M-Files Server version
    Open M-Files Admin, select the server in the left pane, and view the version information in the right panel. Alternatively, check the Windows registry under HKLM\SOFTWARE\Motive\M-Files\<InstallID>\CurrentVersion for the version value.
    Affected if The installed version is below 24.2.13421.15 or is between 24.2.0.0 and 24.8.13981.0 (exclusive).
  2. Verify M-Files Server API is enabled
    In M-Files Admin, navigate to Server Connections > Server API. Confirm that the 'Enable M-Files Server API' checkbox is selected. The API is typically enabled by default on port 2268.
    Affected if The Server API is enabled and accessible to authenticated users.
  3. Review authentication methods for the API
    In M-Files Admin under Authentication Methods, check which authentication types are configured for the M-Files Server API. Look for methods such as Windows Authentication, LDAP, or external authentication providers that allow non-local users to authenticate.
    Affected if External or non-admin authentication is enabled, allowing users beyond local administrators to access the API.

You are affected if your M-Files Server version falls within the vulnerable ranges AND the Server API is enabled with authentication methods that permit authenticated users to make API requests.

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.2.13421.15 / 24.8.13981.0 or later
Fixed in 24.2.13421.1524.8.13981.0
Interim mitigation

Update M-Files Server to version 24.8.13981.0 or later, or apply the relevant LTS SR2/SR6 patches for LTS 24.2 and LTS 23.8 releases.

Recommended fix High confidence

24.8.13981.0 (or LTS 24.2.13421.15 SR2, or LTS 23.8.12892.0 SR6)

  1. Identify the current M-Files Server version in use
  2. Backup all M-Files Server data, configuration, and databases
  3. Download M-Files Server version 24.8.13981.0, or LTS 24.2.13421.15 SR2, or LTS 23.8.12892.0 SR6 from the official M-Files portal (empower.m-files.com or product.m-files.com)
  4. Stop the M-Files Server service before upgrading
  5. Install the downloaded fixed version following M-Files upgrade documentation
  6. Verify the upgrade completed successfully and the service starts properly
  7. Test that the path traversal vulnerability is no longer exploitable

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6789 — 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-2024-6789 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