dbcve.org
Classic WebApplication · M Files

CVE-2023-3406

MEDIUM · 6.5 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 →
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
Path Traversal issue in M-Files Classic Web versions below 23.6.12695.3 and LTS Service Release Versions before 23.2 LTS SR3 allows authenticated user to read some restricted files on the web server

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

Path traversal vulnerability in M-Files Classic Web allows authenticated users to read restricted files on the web server by manipulating file path inputs with directory traversal sequences (e.g., ../). The vulnerability affects versions below 23.6.12695.3 and LTS versions before 23.2 LTS SR3.

MitigationUpgrade M-Files Classic Web to version 23.6.12695.3 or later, or to 23.2 LTS SR3 or later. Restrict web server file permissions as a defense-in-depth measure until the upgrade can be applied.

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
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. Confirm M-Files Classic Web is installed
    Check the installed programs on the Windows server for M-Files, or look for the M-Files web application files in the installation directory (commonly in C:\Program Files\M-Files or similar).
    Affected if M-Files Classic Web is not installed on the system.
  2. Identify the installed M-Files version
    Open M-Files Admin, navigate to the server in the left pane, and view the version information in the right panel. Alternatively, check the About or Version info in the M-Files desktop client or server administration tools.
    Affected if The installed version is less than 23.6.12695.3, or is version 23.2 without LTS SR3 applied.
  3. Verify Classic Web interface is enabled
    In M-Files Admin, check the vault properties or server settings for web server configuration. Confirm that Classic Web (the legacy web interface) is enabled and accessible.
    Affected if Classic Web interface is disabled - the vulnerability would not be exploitable in this case.
  4. Confirm user authentication is configured
    In M-Files Admin, verify that user authentication is set up for the vault accessible via Classic Web. The vulnerability requires an authenticated user session.
    Affected if No users are authenticated or no authentication method is configured for Classic Web access.

The environment is affected if M-Files Classic Web is installed with a version below 23.6.12695.3 (or version 23.2 without LTS SR3), the Classic Web interface is enabled, and user authentication is configured.

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 Classic Web to version 23.6.12695.3 or later, or to 23.2 LTS SR3 or later. Restrict web server file permissions as a defense-in-depth measure until the upgrade can be applied.

Recommended fix High confidence

M-Files Classic Web 23.6.12695.3 or later, or 23.2 LTS SR3 (LTS branch)

  1. 1. Back up your current M-Files Classic Web installation and configuration
  2. 2. Download M-Files Classic Web version 23.6.12695.3 or later from the official M-Files download portal
  3. 3. Alternatively, if using the LTS branch, download version 23.2 LTS SR3 or later
  4. 4. Apply the upgrade following the standard M-Files upgrade procedure documented in their admin guide
  5. 5. Verify the upgrade was successful by checking the version number in the Classic Web interface
  6. 6. Test that the path traversal vulnerability is remediated by confirming users can no longer access restricted files outside their permitted directories

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

Fix this in Classic Web Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
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,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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