mycomplianceoffice vulnerabilities
Recent CVEs affecting mycomplianceoffice products. 8 tracked.
mycomplianceoffice has 8 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2026-07-01. Highest priority: CVE-2026-53906 (score 45/100).
- CVE-2026-53906 HIGH 8.2 DOWNGRADE MCO is vulnerable to Path Disclosure and Path Traversal in file handling functionality related to data export
- CVE-2026-53903 HIGH 8.1 DOWNGRADE MCO is vulnerable to an Insecure Direct Object Reference (IDOR) vulnerability in the /customer/servlet/mco/web
- CVE-2026-53904 HIGH 7.1 DOWNGRADE MCO is vulnerable to Account Denial of Service due to improper implementation of password reset functionality
- CVE-2026-53905 HIGH 7.1 DOWNGRADE MCO does not properly enforce authorization checks in the /customer/servlet/mco/webapi/admin-view-hierarchy/ge
- CVE-2026-53909 MEDIUM 6.5 DOWNGRADE MCO does not correctly validate types of uploaded files
- CVE-2026-53902 MEDIUM 6.5 DOWNGRADE MCO does not properly enforce authorization checks in the /customer/servlet/mco/webapi/profile-sections/group-
- CVE-2026-53907 MEDIUM 5.4 DOWNGRADE MCO is vulnerable to Stored Cross‑Site Scripting (XSS) via the application logo upload functionality
- CVE-2026-53908 MEDIUM 4.3 DOWNGRADE MCO is vulnerable to User Enumeration through authentication-related functionalities
FAQ
How do I fix mycomplianceoffice vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is mycomplianceoffice being exploited right now?
None of the tracked mycomplianceoffice CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which mycomplianceoffice CVE should I patch first?
CVE-2026-53906 currently ranks highest (45/100): MCO is vulnerable to Path Disclosure and Path Traversal in file handling functionality related to data export .