dbcve.org
Web CompanionApplication · M Files

CVE-2023-5523

HIGH · 7.8 CVSS v3.1 Published 2023-10-20
Fix available
A fix is available. Upgrade to 23.8 / 23.10 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
Execution of downloaded content flaw in M-Files Web Companion before release version 23.10 and LTS Service Release Versions before 23.8 LTS SR1 allows Remote Code Execution

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 remote code execution vulnerability exists in M-Files Web Companion versions prior to 23.10 and before 23.8 LTS SR1. The flaw allows execution of downloaded content, likely due to insufficient validation of files or scripts fetched by the Web Companion component, enabling an attacker to execute arbitrary code on the affected system.

MitigationUpdate M-Files Web Companion to version 23.10 or later, or to 23.8 LTS SR1 or later. Prioritize patching given the high CVSS score and RCE capability.

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
Web CompanionApplication
Affected:< 23.8>= 23.3, < 23.10= 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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Locate M-Files Web Companion installation
    Search for 'Web Companion' in the M-Files installation directory, typically under C:\Program Files\M-Files or C:\Program Files (x86)\M-Files, or check services named 'M-Files Web Companion'
    Affected if Web Companion is installed and running
  2. Identify installed Web Companion version
    Right-click the M-Files Web Companion DLL or executable, select Properties, then view the Version tab. Alternatively, check the M-Files Server Admin guide for the version command-line tool.
    Affected if Version cannot be determined or is within affected range < 23.8, 23.3 to < 23.10, or = 23.8
  3. Confirm Web Companion is exposed via HTTP/HTTPS
    Check M-Files Server configuration for Web Companion URL bindings, typically on ports 80/443 or custom ports. Verify the Web Companion endpoint is accessible from network.
    Affected if Web Companion endpoint is accessible externally or on trusted networks
  4. Verify file download feature is enabled
    Check M-Files Web Companion settings in M-Files Admin console for content download or file fetch capabilities.
    Affected if Download or content fetch features are enabled in Web Companion configuration

If M-Files Web Companion is installed with a version lower than 23.10 (specifically < 23.8, or between 23.3 and 23.9.x, or exactly 23.8) and the Web Companion web interface is accessible, the environment is likely affected by this RCE vulnerability.

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 / 23.10 or later
Fixed in 23.823.10
Interim mitigation

Update M-Files Web Companion to version 23.10 or later, or to 23.8 LTS SR1 or later. Prioritize patching given the high CVSS score and RCE capability.

Recommended fix High confidence

23.10 (standard release) or 23.8 LTS SR1 (LTS release)

  1. 1. Identify your current Web Companion version in the M-Files admin interface or by checking the installed application
  2. 2. Download the fixed version from the official M-Files download portal (product.m-files.com or empower.m-files.com) - choose either release version 23.10 or LTS version 23.8 LTS SR1 depending on your deployment preference
  3. 3. Back up your current M-Files configuration and any custom Web Companion settings
  4. 4. Install or apply the update following standard M-Files upgrade procedures (typically requires stopping the M-Files Server service, applying the update, then restarting the service)
  5. 5. Verify the Web Companion version shows the updated release after installation
  6. 6. Test that Web Companion functionality works correctly in your environment

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

Fix this in Web Companion Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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