Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with low-privileged MCO account
-
DeliveryEnumerate group IDs via group picker endpoint
-
ExploitSend crafted request to group-membership endpoint
-
ExecutionAdd self to privileged group
-
ImpactInherit elevated permissions
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Privilege assignment review
|
| Exploitation Conditions | Requires a valid authenticated MCO account (CVSS PR:L) that can reach the /customer/servlet/mco/webapi/profile-sections/group-membership endpoint over the network (AV:N), plus a valid target group ID. That group ID is obtainable through the application's own /customer/servlet/mco/webapi/group/picker/groups endpoint when the user has the necessary permissions, or otherwise inferred through brute-force enumeration. No user interaction, no non-default configuration, and no elevated privileges are required; the primary limiting factors are that the attacker must already hold a working low-privileged session and must know or guess a privileged group's ID. Confirmed only against MCO version 25.3.3.1. |
| Impact | The vendor CVSS 4.0 score is 7.1 (High) with vector AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N, indicating a network-reachable, low-complexity attack requiring low privileges (an existing authenticated account) and no user interaction, yielding high integrity impact (unauthorized permission changes) with only low confidentiality and no availability impact - consistent with privilege escalation rather than data destruction. No EPSS score, KEV entry, or SSVC decision was supplied, so probabilistic and government-triage signals are unavailable, and there is no public exploit identified at time of analysis. Realistic priority is moderate-to-high for organizations running MCO because the prerequisite (any valid low-privileged account) is easily met by insiders or attackers who have phished a single credential, and the group-ID enumeration path is documented within the app itself. Key caveat: affected-version data is incomplete - only 25.3.3.1 is confirmed and the vendor was unreachable, so defenders cannot rely on a clean 'fixed version' boundary and should treat all deployed versions as potentially vulnerable until tested. |
| Exploit ScenarioDerived | A low-privileged employee, or an attacker who has compromised one standard user credential, logs into MCO, calls the group picker endpoint to list valid group IDs, then sends a crafted request to the group-membership endpoint adding their own account to a privileged group. With the missing authorization check the change succeeds and the attacker gains elevated permissions without admin approval. No public exploit is identified, but per the CVSS vector the attack is low-complexity and needs only standard authenticated access. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 01, 2026
Privilege escalation in MyComplianceOffice (MCO) compliance platform version 25.3.3.1 lets an authenticated user add themselves to arbitrary groups via the /customer/servlet/mco/webapi/profile-sections/group-membership endpoint, which fails to enforce authorization on group changes. By supplying a valid group ID - obtainable through the application's own group picker API or guessable via brute force - a low-privileged account can inherit the permissions of higher-privileged groups. Reported by CERT-PL; no public exploit identified at time of analysis and the flaw is not listed in CISA KEV.
RemediationAI
No vendor-released patch identified at time of analysis, as CERT-PL was unable to establish contact with MyComplianceOffice. Organizations should contact the vendor directly to confirm a fixed release and request server-side authorization enforcement on the /customer/servlet/mco/webapi/profile-sections/group-membership endpoint. As compensating controls until a fix exists: restrict or monitor access to the group-membership and group picker (/customer/servlet/mco/webapi/group/picker/groups) endpoints at a reverse proxy or WAF so group-modification requests from non-administrative sessions are blocked (side effect: legitimate self-service group changes, if any, would break); enable and alert on audit logging of group-membership changes to detect anomalous self-additions to privileged groups (side effect: increased log volume); and periodically review current memberships for unauthorized entries. Reference the CERT-PL advisory at https://cert.pl/en/posts/2026/07/CVE-2026-53902.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
MCO (MyComplianceOffice) is a governance, risk, and compliance (GRC) web application used by regulated firms to manage employee compliance obligations. The affected component is a Java servlet-backed web API - the /customer/servlet/mco/... path indicates a servlet container. The root cause is CWE-266 (Incorrect Privilege Assignment): the group-membership modification endpoint trusts a client-supplied group ID and updates the caller's membership without verifying the caller is authorized to join that group. Because group IDs can be enumerated through a legitimate sibling endpoint (/customer/servlet/mco/webapi/group/picker/groups) or inferred by brute force, the missing server-side authorization check converts an ordinary authenticated session into a vector for vertical privilege gain. The CPE cpe:2.3:a:mycomplianceoffice:mco:*:*:*:*:*:*:*:* confirms vendor 'mycomplianceoffice' and product 'mco', with the version wildcard reflecting that only 25.3.3.1 was confirmed while other versions remain untested.
Know when Mco gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N
Network-reachable endpoint (AV:N), simple request (AC:L), needs an existing low-priv account (PR:L), no interaction; unauthorized group changes give high integrity, low confidentiality, no availability, scope unchanged.
Primary rating from Vendor (CERT-PL).
CVSS VectorVendor: CERT-PL
DescriptionCVE.org
MCO does not properly enforce authorization checks in the /customer/servlet/mco/webapi/profile-sections/group-membership endpoint. An authenticated user can modify their group membership without proper authorization checks, allowing privilege escalation. An attacker can add themselves to arbitrary groups by supplying a valid group ID, which can be obtained via other application functionalities (e.g. /customer/servlet/mco/webapi/group/picker/groups), provided he has necessary permissions, or potentially inferred through brute-force techniques.
Because vendor contact attempts were unsuccessful, the vulnerability has only been confirmed in version 25.3.3.1 but may also affect other versions.
Executive ViewAI
A privilege escalation vulnerability in MyComplianceOffice (MCO) version 25.3.3.1 allows authenticated internal users to self-assign membership to arbitrary groups, potentially granting unauthorized access to sensitive compliance data and system functions. This undermines role-based access controls and could enable unauthorized access to compliance documents, audit trails, and administrative functions depending on group assignments. Organizations using MCO should assume internal users can currently bypass intended permission boundaries.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict API access to the /customer/servlet/mco/webapi/profile-sections/group-membership endpoint to authorized administrators only via WAF, API gateway, or network segmentation; (2) Disable user self-service group management functionality if operationally feasible; (3) Implement continuous monitoring and alerting on all group membership changes with mandatory administrative review workflows; (4) Enforce principle of least privilege for initial group assignments to minimize blast radius if unauthorized changes occur; (5) Conduct immediate comprehensive audit of all existing group memberships to identify and remediate unauthorized or suspicious assignments.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
User enumeration in MyComplianceOffice (MCO) version 25.3.3.1 allows unauthenticated remote attackers to identify valid
Account denial-of-service in MyComplianceOffice MCO 25.3.3.1 enables a remote attacker to permanently lock a targeted us
Unrestricted file upload in MyComplianceOffice MCO version 25.3.3.1 allows an authenticated low-privileged attacker to u
Insecure Direct Object Reference in MyComplianceOffice MCO version 25.3.3.1 allows authenticated users to retrieve tradi
MCO's compliance management platform exposes administrator ACL tree structures to any authenticated low-privileged user
Path traversal and path disclosure in MyComplianceOffice MCO's file handling functionality expose authenticated high-pri
Stored XSS in MyComplianceOffice MCO version 25.3.3.1 allows a privileged attacker with logo-upload rights to plant mali
EUVD-2026-40948
GHSA-rgv6-j8h9-46fv
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB