Skip to main content

MyComplianceOffice MCO CVE-2026-53909

| EUVDEUVD-2026-40955 MEDIUM
Unrestricted Upload of File with Dangerous Type (CWE-434)
2026-07-01 CERT-PL GHSA-5v97-p7p8-r448
5.3
CVSS 4.0 · Vendor: CERT-PL
Share

Severity by source

Vendor (CERT-PL) PRIMARY
5.3 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
vuln.today AI
5.0 MEDIUM

Low-privileged network access required; scope changed to reflect downstream integrity impact from arbitrary file placement; no confidentiality or availability impact confirmed.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N

Primary rating from Vendor (CERT-PL).

CVSS VectorVendor: CERT-PL

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
X

Lifecycle Timeline

2
Analysis Generated
Jul 01, 2026 - 13:21 vuln.today
CVE Published
Jul 01, 2026 - 11:59 cve.org
MEDIUM 5.3

DescriptionCVE.org

MCO does not correctly validate types of uploaded files. File upload validation functionality relies only on client-side checks, which can be bypassed. An authorized, low-privileged attacker can upload files with arbitrary types to the server.

Because vendor contact attempts were unsuccessful, the vulnerability has only been confirmed in version 25.3.3.1 but may also affect other versions.

AnalysisAI

Unrestricted file upload in MyComplianceOffice MCO version 25.3.3.1 allows an authenticated low-privileged attacker to upload files of arbitrary types by bypassing client-side-only validation controls. The CVSS 4.0 vector confirms network-accessible exploitation with low complexity, requiring only a valid low-privileged account and a web proxy to intercept and modify upload requests. No public exploit has been identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog.

Technical ContextAI

The root cause is CWE-434 (Unrestricted Upload of File with Dangerous Type), a class of vulnerability arising when applications delegate file type enforcement exclusively to browser-side JavaScript rather than performing authoritative validation on the server. In MCO (CPE: cpe:2.3:a:mycomplianceoffice:mco:*:*:*:*:*:*:*:*), a compliance management platform by MyComplianceOffice, the upload mechanism checks file types only in the client, meaning any standard proxy tool (e.g., Burp Suite, OWASP ZAP) can intercept the POST request and substitute a different file before it reaches the server. Server-side controls such as MIME type inspection, extension allowlisting, and file magic-byte validation are absent or insufficient. The CVSS 4.0 vector's subsequent-system integrity impact (SI:L) indicates the uploaded file can affect systems or processes beyond the immediate upload handler.

RemediationAI

No vendor-released patch has been identified at time of analysis due to unsuccessful vendor contact attempts documented by CERT-PL. Organizations should monitor https://mco.mycomplianceoffice.com/ and https://cert.pl/en/posts/2026/07/CVE-2026-53902 for any vendor-issued fix or updated advisory. As compensating controls, administrators should implement server-side file type validation that inspects MIME type headers, enforces an extension allowlist, and verifies file magic bytes before accepting any upload - note that relying on the Content-Type header alone is insufficient, as this is also attacker-controlled. Uploaded files should be stored outside web-accessible directories and served only through a controller that enforces content-type on delivery, preventing direct execution. Restricting file upload access to only the minimum set of users with a demonstrated business need reduces the attacker pool given the PR:L prerequisite. Auditing server logs for unexpected file extensions in upload endpoints can help detect exploitation attempts in the interim.

Share

CVE-2026-53909 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy