dbcve.org
Classic WebApplication · M Files

CVE-2023-3425

MEDIUM · 5.3 CVSS v3.1 Published 2023-08-25
Fix available
A fix is available. Upgrade to 23.2 / 23.6.12695.3 or later.
See remediation →
62/100
Remediation priority · Elevated
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
Out-of-bounds read issue in M-Files Server versions below 23.8.12892.6 and LTS Service Release Versions before 23.2 LTS SR3 allows unauthenticated user to read restricted amount of bytes from memory.

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

Out-of-bounds memory read vulnerability in M-Files Server allows unauthenticated users to read a limited amount of bytes from process memory, potentially exposing sensitive information. The vulnerability affects versions below 23.8.12892.6 and LTS versions before 23.2 LTS SR3.

MitigationUpgrade M-Files Server to version 23.8.12892.6 or later, or to version 23.2 LTS SR3 or later for LTS 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
Classic WebApplication
Affected:< 23.2< 23.6.12695.3= 23.2

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Verify M-Files Server installation
    Check if M-Files Server is installed on the system by looking for the M-Files application in installed programs or services
    Affected if M-Files Server is present on the system
  2. Determine M-Files Server version
    Retrieve the installed version of M-Files Server through the application itself, administrative interface, or installed programs list
    Affected if Version is below 23.8.12892.6 or is an LTS version below 23.2 LTS SR3
  3. Check for M-Files Classic Web component
    Determine if M-Files Classic Web is also installed as a separate component
    Affected if M-Files Classic Web is installed with version < 23.2, < 23.6.12695.3, or exactly version 23.2
  4. Compare against affected version ranges
    Match the installed version numbers against the affected ranges: < 23.8.12892.6, or LTS versions before 23.2 LTS SR3, or Classic Web versions < 23.2, < 23.6.12695.3, or = 23.2
    Affected if Any installed version falls within these affected ranges

The environment is affected if M-Files Server version is below 23.8.12892.6, or below 23.2 LTS SR3 for LTS releases, or if M-Files Classic Web is installed with version less than 23.2, less than 23.6.12695.3, or exactly 23.2.

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.2 / 23.6.12695.3 or later
Fixed in 23.223.6.12695.3
Interim mitigation

Upgrade M-Files Server to version 23.8.12892.6 or later, or to version 23.2 LTS SR3 or later for LTS releases.

Recommended fix High confidence

23.8.12892.6 (standard) or 23.2 LTS SR3 (LTS)

  1. Identify your current M-Files Server version by checking the About section in M-Files Admin or M-Files Client
  2. If running a version before 23.8.12892.6 (standard release), plan upgrade to version 23.8.12892.6 or later
  3. If running LTS version before 23.2 LTS SR3, plan upgrade to 23.2 LTS SR3 or later
  4. Before upgrading, backup your M-Files Vault and server configuration
  5. Download the appropriate installer from the M-Files customer portal at my.m-files.com or your designated download location
  6. Stop the M-Files Server service before applying the upgrade
  7. Run the installer and follow the on-screen prompts to complete the upgrade
  8. After upgrade, verify the M-Files Server service starts successfully
Caveat Review M-Files release notes for any compatibility considerations or deprecated features between your current version and the target version

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

Fix this in Classic Web Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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