dbcve.org
M Files ServerApplication · M Files

CVE-2023-6239

HIGH · 8.8 CVSS v3.1 Published 2023-11-28
Fix available
A fix is available. Upgrade to 23.11.13168.7 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Under rare conditions, the effective permissions of an object might be incorrectly calculated if the object has a specific configuration of metadata-driven permissions in M-Files Server versions 23.9, 23.10, and 23.11 before 23.11.13168.7, potentially enabling unauthorized access to the object.

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 has a permission calculation flaw in versions 23.9 through 23.11 before 23.11.13168.7 where metadata-driven permissions are incorrectly computed under specific, rare configurations, potentially granting unauthorized access to objects.

MitigationUpgrade M-Files Server to version 23.11.13168.7 or later, or apply the vendor-supplied 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:>= 23.11, < 23.11.13168.7= 23.9= 23.10

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Determine M-Files Server version
    Open M-Files Admin, go to the server connection, and view the version information in the server properties or status area. Alternatively, check the version of the M-Files Server service executable in the installation directory.
    Affected if The installed version is 23.9, 23.10, or any version from 23.11.0 through 23.11.13168.6 (the versions before 23.11.13168.7).
  2. Verify metadata-driven permissions are configured
    In M-Files Admin, open the vault properties for any configured vaults. Navigate to the Permissions or Security settings. Look for permission rules that are based on object metadata (such as property-based conditions, class-based permissions, or custom permission definitions) rather than standard inheritance only.
    Affected if Metadata-driven or property-based permission rules are defined in vault security settings.
  3. Identify vaults using conditional metadata permissions
    In M-Files Admin, review each vault's permission structure. Check for permission definitions that reference specific property values, classes, or state transitions as conditions for access. These are the rare configurations that can trigger the flawed permission calculation.
    Affected if The vault has conditional permission rules that depend on metadata values or object properties.

You are affected if your M-Files Server version falls within 23.9, 23.10, or 23.11.x before 23.11.13168.7 AND you have vaults configured with metadata-driven (property-based) conditional permission rules.

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.11.13168.7 or later
Fixed in 23.11.13168.7
Interim mitigation

Upgrade M-Files Server to version 23.11.13168.7 or later, or apply the vendor-supplied patch.

Recommended fix High confidence

23.11.13168.7

  1. 1. Back up the M Files Server database and configuration settings before proceeding with any update.
  2. 2. Download M Files Server version 23.11.13168.7 from the official M Files download portal (www.m-files.com or empower.m-files.com).
  3. 3. Follow the M Files standard upgrade procedure documented in the product administration guide.
  4. 4. After installation, verify the server is running the correct version through the M Files admin interface.
  5. 5. Test that permission calculations are functioning correctly for objects using metadata-driven permissions.
Caveat Review M Files release notes for version 23.11.13168.7 for any configuration or behavior changes; standard upgrade precautions apply.

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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