Web CompanionApplication · M Files

CVE-2023-5524

HIGH · 7.3 CVSS v3.1 Published 2023-10-20

Fix available

A fix is available. Upgrade to 23.8 / 23.10 or later.

See remediation →

73/100

Remediation priority · Elevated

Official description

NVD · unedited

Insufficient blacklisting in M-Files Web Companion before release version 23.10 and LTS Service Release Versions before 23.8 LTS SR1 allows Remote Code Execution via specific file types

Technical summary

dbcve analysis · moderate confidence

Insufficient blacklisting in M-Files Web Companion allows attackers to upload and execute malicious files by bypassing file type restrictions. The vulnerability exists in versions prior to 23.10 and LTS versions before 23.8 LTS SR1, where certain dangerous file types are not properly blocked, enabling remote code execution.

MitigationUpgrade M-Files Web Companion to version 23.10 or later (regular release) or 23.8 LTS SR1 or later (LTS release) to implement proper file type blacklisting.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Web CompanionApplication

Affected:< 23.8>= 23.3, < 23.10= 23.8

CVSS breakdown

From the vector

Attack vector: Local
Complexity: Low
Privileges: Low
User interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Confirm M-Files Web Companion is installed

Check the installed programs on the M-Files server or look for M-Files Web Companion in the M-Files installation directory

Affected if M-Files Web Companion is present on the system
Determine the installed version of M-Files Web Companion

Access the M-Files Admin application or check the version information for M-Files Web Companion in the installed programs list or program directory

Affected if The version is less than 23.8, equals 23.8, or is between 23.3 and 23.9 (inclusive)
Verify if Web Companion is enabled and accessible

Check the M-Files Server configuration to confirm Web Companion is running and accessible via HTTP/HTTPS

Affected if Web Companion is enabled and exposed to network users
Confirm file upload functionality is available

Review the M-Files Web Companion settings or access the web interface to determine if users can upload files through the web client

Affected if File upload capability is permitted for users in the web interface

A user is affected if M-Files Web Companion is installed with a version in the range of 23.3 to 23.9 or exactly version 23.8, and the web upload feature is accessible to users.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 23.8 / 23.10 or later

Fixed in 23.823.10

Interim mitigation

Upgrade M-Files Web Companion to version 23.10 or later (regular release) or 23.8 LTS SR1 or later (LTS release) to implement proper file type blacklisting.

Recommended fix High confidence

23.10 or 23.8 LTS SR1

1. Identify the current version of M-Files Web Companion by accessing the M-Files admin interface or checking the application metadata
2. Navigate to the official M-Files download portal (product.m-files.com or empower.m-files.com) and obtain the fixed release version
3. If running version 23.8, upgrade to 23.8 LTS SR1; otherwise upgrade to release version 23.10
4. Follow the standard M-Files upgrade procedure: back up the existing configuration and vault data, stop the M-Files services, apply the Web Companion update
5. Restart M-Files services and verify the Web Companion version reflects the updated release
6. Test that file upload functionality works correctly and that malicious file types are now properly blocked

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

Fix this in Web Companion Scoped from the published advisory

Consultation4.0 h
Implementation8.0 h
Testing8.0 h
Review / QA4.0 h

24.0 hours of engineering $4,160

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-5524 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2023-5524?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 23.8 / 23.10 or later

Severity 7.3 High

Exploit likelihood EPSS, next 30 days 0.3%

Affects: Web Companion

Remediation

Need this fixed?

Fix this in Web Companion 24 hrs · Moderate

Typical engagement from $4,160

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2023-5524 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References