dbcve.org
M Files ServerApplication · M Files

CVE-2023-3405

HIGH · 7.5 CVSS v3.1 Published 2023-06-27
Fix available
A fix is available. Upgrade to 23.6.12695.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Unchecked parameter value in M-Files Server in versions before 23.6.12695.3 (excluding 23.2 SR2 and newer) allows anonymous user to cause denial of service

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

M-Files Server contains an unchecked parameter value vulnerability that allows unauthenticated (anonymous) users to trigger a denial of service condition. The vulnerability exists in versions prior to 23.6.12695.3 (with certain 23.2 SR2 and newer versions excluded from impact).

MitigationUpgrade M-Files Server to version 23.6.12695.3 or later. Prior to upgrade, ensure current configuration backups exist and plan for appropriate maintenance downtime.

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:< 23.6.12695.3

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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 installation
    Locate the M-Files Server installation directory, typically in C:\Program Files\M-Files or C:\Program Files (x86)\M-Files on Windows servers. Check for the server executable (M-Files Server.exe) or check Windows Services for the 'M-Files Server' service.
    Affected if M-Files Server is not installed on the system
  2. Determine installed M-Files Server version
    Open Windows Services, locate the M-Files Server service, right-click and select Properties. The version is shown in the 'Path to executable' or check the file version of M-Files Server.exe in the installation directory. Alternatively, open M-Files Admin, expand the server node, and view the version information in the right pane.
    Affected if The installed version is less than 23.6.12695.3
  3. Verify anonymous access configuration
    Open M-Files Admin, expand the server vault, go to Authentication > Anonymous Access (or External unauthenticated access settings). Check whether anonymous or unauthenticated access is enabled for any vaults or connections.
    Affected if Anonymous or unauthenticated access is enabled on the M-Files Server
  4. Check excluded version ranges
    If the installed version is 23.2 SR2 or newer but less than 23.6.12695.3, consult M-Files release documentation to determine if your specific 23.2.x version or 23.x build is explicitly listed as excluded from impact. This may require reviewing M-Files security advisory details.
    Affected if The version is not in the explicitly excluded range and is below 23.6.12695.3

A system is affected if M-Files Server is installed with a version below 23.6.12695.3 and anonymous or unauthenticated access is enabled, unless the specific version is confirmed to be in an excluded range.

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 23.6.12695.3 or later
Fixed in 23.6.12695.3
Interim mitigation

Upgrade M-Files Server to version 23.6.12695.3 or later. Prior to upgrade, ensure current configuration backups exist and plan for appropriate maintenance downtime.

Recommended fix High confidence

23.6.12695.3

  1. Identify the current M-Files Server version by checking the application or server administration interface
  2. Access the official M-Files support portal (empower.m-files.com or product.m-files.com) to obtain version 23.6.12695.3 or later
  3. Create a full backup of the M-Files database and all configuration files before proceeding
  4. Stop the M-Files Server service to prevent active connections during the upgrade
  5. Install M-Files Server version 23.6.12695.3 using the standard installation/upgrade process documented by M-Files
  6. Verify the upgrade was successful by confirming the installed version matches 23.6.12695.3 or later
  7. Restart the M-Files Server service and verify normal operation
Caveat Review M-Files release notes for any breaking changes or required configuration updates between your current version and 23.6.12695.3

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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