MyComplianceOffice MCO 25.3.3.1 PdfStatement Endpoint fetchPdfStatement authorization

Summaryinfo

A vulnerability was found in MyComplianceOffice MCO 25.3.3.1. It has been rated as problematic. Impacted is an unknown function of the file /customer/servlet/mco/webapi/trading-document/fetchPdfStatement of the component PdfStatement Endpoint. Performing a manipulation results in authorization. This vulnerability is identified as CVE-2026-53903. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in MyComplianceOffice MCO 25.3.3.1. This affects an unknown function of the file /customer/servlet/mco/webapi/trading-document/fetchPdfStatement of the component PdfStatement Endpoint. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. This is going to have an impact on confidentiality. The summary by CVE is:

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.

The weakness was released with AFINE Team. The advisory is shared at cert.pl. This vulnerability is uniquely identified as CVE-2026-53903 since 06/11/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/01/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• MyComplianceOffice

Name

• MCO

Version

• 25.3.3.1

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion