dbcve.org
M FilesApplication

CVE-2023-4479

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-04
Fix available
A fix is available. Upgrade to 23.8 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 Web versions before 23.8 allows attacker to execute script on users browser via stored HTML document within limited time period.

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

A stored cross-site scripting (XSS) vulnerability in M-Files Web versions before 23.8 allows authenticated attackers to inject malicious HTML or JavaScript into stored documents. When other users view these compromised documents within a limited time window, the attacker's script executes in their browsers, potentially leading to session hijacking or data theft.

MitigationUpgrade M-Files Web to version 23.8 or later to receive the security patch; implement input validation and Content Security Policy headers as additional defense layers.

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 FilesApplication
Affected:< 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. Identify M-Files Web installation and version
    Check the M-Files server for installed M-Files Web component version - typically found in Programs and Features on Windows, or via M-Files Admin console under Web Server settings
    Affected if Installed version is any M-Files Web version before 23.8 (versions 23.7, 23.6, earlier)
  2. Confirm M-Files Web service is running
    Verify the M-Files Web service status via Windows Services console or M-Files Server Administrator - ensure the web interface is accessible
    Affected if The M-Files Web service is running and accessible to users
  3. Check if external/collaborative sharing is enabled
    Review M-Files vault sharing settings in M-Files Admin - look for external sharing or limited time window sharing configurations that allow users to share documents with other users
    Affected if Document sharing with limited time windows is enabled, allowing other users to view documents uploaded by other authenticated users
  4. Verify user authentication is active
    Confirm that M-Files is configured to allow authenticated user access to the web interface - check authentication methods in M-Files Admin under web server configuration
    Affected if Authenticated users can log in and access the web interface to upload/view documents

A user is affected if they are running any M-Files Web version below 23.8 with the web service enabled and user authentication active.

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.8 or later
Fixed in 23.8
Interim mitigation

Upgrade M-Files Web to version 23.8 or later to receive the security patch; implement input validation and Content Security Policy headers as additional defense layers.

Recommended fix Moderate confidence

M-Files 23.8

  1. 1. Verify current M-Files version by accessing the M-Files server administration or checking the About section in the M-Files client.
  2. 2. Back up the M-Files database and configuration settings before proceeding with the upgrade.
  3. 3. Download M-Files version 23.8 or later from the official M-Files download portal (www.m-files.com or empower.m-files.com).
  4. 4. Follow M-Files upgrade documentation to install version 23.8 on the server.
  5. 5. After upgrade, verify that the M-Files Web interface is functioning correctly.
  6. 6. Test that the XSS vulnerability is no longer present by attempting to upload a stored HTML document with malicious script content.

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

Fix this in M Files Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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