MyComplianceOffice MCO 25.3.3.1 Configuration get-acl-tree-structure authorization

Summaryinfo

A vulnerability described as problematic has been identified in MyComplianceOffice MCO 25.3.3.1. Affected is an unknown function of the file /customer/servlet/mco/webapi/admin-view-hierarchy/get-acl-tree-structure of the component Configuration Handler. Such manipulation leads to authorization. This vulnerability is documented as CVE-2026-53905. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in MyComplianceOffice MCO 25.3.3.1. It has been rated as problematic. Affected by this issue is an unknown code block of the file /customer/servlet/mco/webapi/admin-view-hierarchy/get-acl-tree-structure of the component Configuration Handler. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. Impacted is confidentiality. CVE summarizes:

MCO does not properly enforce authorization checks in the /customer/servlet/mco/webapi/admin-view-hierarchy/get-acl-tree-structure endpoint. An authenticated, low-privileged user can retrieve administrator access control structures without proper authorization checks. This may expose sensitive permission mappings and internal configuration details. 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 available at cert.pl. This vulnerability is handled as CVE-2026-53905 since 06/11/2026. The exploitation is known to be easy. The attack may be launched remotely. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of 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 best quality of vulnerability data, you may have to visit 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 best quality of vulnerability data, you may have to visit VulDB.

Discussion