M Files ServerApplication · M Files

CVE-2023-6912

CRITICAL · 9.8 CVSS v3.1 Published 2023-12-20

Fix available

A fix is available. Upgrade to 23.12.13205.0 or later.

See remediation →

100/100

Remediation priority · Urgent

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Lack of protection against brute force attacks in M-Files Server before 23.12.13205.0 allows an attacker unlimited authentication attempts, potentially compromising targeted M-Files user accounts by guessing passwords.

Technical summary

dbcve analysis · high confidence

M-Files Server before version 23.12.13205.0 lacks brute force protection mechanisms such as rate limiting, account lockout, or CAPTCHA, allowing unlimited authentication attempts against user accounts.

MitigationUpgrade M-Files Server to version 23.12.13205.0 or later. As an interim measure, implement network-level access controls or multi-factor authentication, and monitor for suspicious authentication patterns.

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

Affected products & versions

NVD · CPE data

M Files ServerApplication

Affected:< 23.12.13205.0

CVSS breakdown

From the vector

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

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

Am I affected?

dbcve checks

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

Identify M-Files Server installation

Locate the M-Files Server installation through Windows Programs and Features, or check the M-Files Admin application, or query the Windows Registry under HKLM\SOFTWARE\M-Files for the installed version.

Affected if M-Files Server is installed on the system.
Determine installed M-Files Server version

Retrieve the exact version number of M-Files Server. In the M-Files Admin interface, navigate to the server properties or About section. From command line, you may run 'm-filesadmin /version' if available, or inspect the executable properties of the M-Files Server binary.

Affected if Unable to confirm the version is 23.12.13205.0 or later.
Compare version against vulnerability threshold

Take the installed version string (for example, 23.11.12800.0) and compare it numerically to the fixed version 23.12.13205.0. Ensure the major.minor.build components all meet or exceed the threshold.

Affected if The installed version is less than 23.12.13205.0 (for example, 23.12.13204.0 or any earlier release).

If the installed M-Files Server version is below 23.12.13205.0, the environment lacks built-in brute force protection and is affected by this CVE.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 23.12.13205.0 or later

Fixed in 23.12.13205.0

Interim mitigation

Upgrade M-Files Server to version 23.12.13205.0 or later. As an interim measure, implement network-level access controls or multi-factor authentication, and monitor for suspicious authentication patterns.

Recommended fix High confidence

23.12.13205.0 or later

Download M-Files Server version 23.12.13205.0 or later from the official M-Files portal (empower.m-files.com or product.m-files.com)
Review the M-Files upgrade documentation for your current version to ensure compatibility
Create a complete backup of your M-Files database and configuration before proceeding
Stop the M-Files Server service to prevent data inconsistencies during upgrade
Run the M-Files Server installer for version 23.12.13205.0 or newer
Follow the on-screen upgrade wizard, selecting the upgrade option
Verify the installation completed successfully and the service starts without errors
Confirm the brute force protection is now active by checking authentication settings in M-Files Admin

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

Fix this in M Files Server Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing4.0 h
Review / QA2.0 h

12.0 hours of engineering $2,080

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,328.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2023-6912?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 23.12.13205.0 or later

Severity 9.8 Critical

Exploit likelihood EPSS, next 30 days 1.0%

Affects: M Files Server

Remediation

A high-priority fix

Fix this in M Files Server 12 hrs · Moderate

Typical engagement from $2,080

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2023-6912 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References