CVE-2026-53903: CWE-639 Authorization Bypass Through User-Controlled Key in MyComplianceOffice MCO
MCO is vulnerable to an Insecure Direct Object Reference (IDOR) vulnerability in the /customer/servlet/mco/webapi/trading-document/fetchPdfStatement endpoint. The application does not properly validate whether an authenticated user is authorized to access a requested document, allowing direct retrieval based on a user-supplied identifier. An attacker can access trading documents belonging to other users by providing a valid document ID. Although exploitation requires guessing the identifier, predictable ID patterns enable feasible enumeration, leading to unauthorized disclosure of sensitive information. Because vendor contact attempts were unsuccessful, the vulnerability has only been confirmed in version 25.3.3.1 but may also affect other versions.
AI Analysis
Technical Summary
CVE-2026-53903 is an authorization bypass vulnerability (CWE-639) in MyComplianceOffice MCO version 25.3.3.1. The vulnerability exists in the fetchPdfStatement API endpoint, which fails to verify that the authenticated user is authorized to access the requested document. Attackers can exploit this by providing a valid document ID, enabling direct retrieval of other users' trading documents. The vulnerability requires low privileges (authenticated user) and no user interaction, with low complexity due to predictable ID patterns. No official fix or remediation guidance is currently available.
Potential Impact
Successful exploitation leads to unauthorized disclosure of sensitive trading documents belonging to other users. This compromises confidentiality of user data within the affected MCO instance. The vulnerability does not require elevated privileges beyond authentication and does not impact system integrity or availability. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since vendor contact attempts were unsuccessful and no official fix is available, organizations should consider restricting access to the affected endpoint, monitoring for suspicious access patterns, and applying compensating controls to limit exposure until a patch or official mitigation is provided.
CVE-2026-53903: CWE-639 Authorization Bypass Through User-Controlled Key in MyComplianceOffice MCO
Description
MCO is vulnerable to an Insecure Direct Object Reference (IDOR) vulnerability in the /customer/servlet/mco/webapi/trading-document/fetchPdfStatement endpoint. The application does not properly validate whether an authenticated user is authorized to access a requested document, allowing direct retrieval based on a user-supplied identifier. An attacker can access trading documents belonging to other users by providing a valid document ID. Although exploitation requires guessing the identifier, predictable ID patterns enable feasible enumeration, leading to unauthorized disclosure of sensitive information. Because vendor contact attempts were unsuccessful, the vulnerability has only been confirmed in version 25.3.3.1 but may also affect other versions.
CVSS v4.0
Score 5.3medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-53903 is an authorization bypass vulnerability (CWE-639) in MyComplianceOffice MCO version 25.3.3.1. The vulnerability exists in the fetchPdfStatement API endpoint, which fails to verify that the authenticated user is authorized to access the requested document. Attackers can exploit this by providing a valid document ID, enabling direct retrieval of other users' trading documents. The vulnerability requires low privileges (authenticated user) and no user interaction, with low complexity due to predictable ID patterns. No official fix or remediation guidance is currently available.
Potential Impact
Successful exploitation leads to unauthorized disclosure of sensitive trading documents belonging to other users. This compromises confidentiality of user data within the affected MCO instance. The vulnerability does not require elevated privileges beyond authentication and does not impact system integrity or availability. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since vendor contact attempts were unsuccessful and no official fix is available, organizations should consider restricting access to the affected endpoint, monitoring for suspicious access patterns, and applying compensating controls to limit exposure until a patch or official mitigation is provided.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- CERT-PL
- Date Reserved
- 2026-06-11T07:44:52.179Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a450d6927e9c797197b9587
Added to database: 07/01/2026, 12:51:53 UTC
Last enriched: 07/01/2026, 13:07:28 UTC
Last updated: 07/01/2026, 21:33:49 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.