dbcve.org
Classic WebApplication · M Files

CVE-2023-2325

MEDIUM · 5.4 CVSS v3.1 Published 2023-10-20
Fix available
A fix is available. Upgrade to 23.10 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Stored XSS Vulnerability in M-Files Classic Web versions before 23.10 and LTS Service Release Versions before 23.2 LTS SR4 and 23.8 LTS SR1allows attacker to execute script on users browser via stored HTML document.

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

A stored cross-site scripting vulnerability in M-Files Classic Web allows authenticated attackers to inject malicious JavaScript into stored HTML documents. When other users view these documents through the Classic Web interface, the embedded script executes in their browsers, potentially enabling session hijacking, credential theft, or unauthorized actions.

MitigationUpgrade M-Files to version 23.10 or later, or to LTS versions 23.2 SR4 / 23.8 SR1 or later. Until patched, restrict document upload permissions to trusted users only and monitor for suspicious content.

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.10= 23.2= 23.8

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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. Check M-Files server version
    Open M-Files Admin and navigate to the About section or Server Properties to view the installed version number. The version is typically displayed as major.minor.patch (e.g., 23.2.0).
    Affected if The installed version is 23.2.x, 23.8.x, or any version earlier than 23.10.x (such as 23.0.x, 22.x, or older)
  2. Verify Classic Web interface is enabled
    In M-Files Admin, go to Server Settings > Web Server configurations and locate the Classic Web interface settings. Confirm whether Classic Web is enabled and accessible to users.
    Affected if Classic Web interface is enabled and accessible to authenticated users in your environment
  3. Identify users with document upload permissions
    In M-Files Admin, review vault permissions under the Users and Groups section. Check which roles or users have Create, Add, or Upload permissions for documents, particularly HTML files.
    Affected if Non-administrative or untrusted users have permissions to upload or create documents in the vault

You are affected if your M-Files server version is 23.2, 23.8, or any version below 23.10 AND the Classic Web interface is enabled with document upload permissions granted to users who could inject malicious content.

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.10 or later
Fixed in 23.10
Interim mitigation

Upgrade M-Files to version 23.10 or later, or to LTS versions 23.2 SR4 / 23.8 SR1 or later. Until patched, restrict document upload permissions to trusted users only and monitor for suspicious content.

Recommended fix Moderate confidence

Upgrade to M-Files Classic Web 23.10+ (standard) OR 23.2 LTS SR4+ OR 23.8 LTS SR1+

  1. Identify the currently installed M-Files Classic Web version by checking the M-Files server administration
  2. If running Classic Web version < 23.10, plan upgrade to version 23.10 or later
  3. If running LTS version 23.2.x, upgrade to 23.2 LTS SR4 or later
  4. If running LTS version 23.8.x, upgrade to 23.8 LTS SR1 or later
  5. After upgrade, verify the M-Files Classic Web client loads correctly and test that stored HTML documents no longer execute arbitrary scripts
  6. Review M-Files release notes for any additional migration or post-upgrade requirements

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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