dbcve.org
MycomplianceofficeApplication

CVE-2026-53905

HIGH · 7.1 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The /customer/servlet/mco/webapi/admin-view-hierarchy/get-acl-tree-structure endpoint lacks proper authorization checks, allowing any authenticated user—including low-privileged accounts—to retrieve administrator-level access control tree structures. This exposes sensitive permission mappings and internal RBAC configuration details.

MitigationImplement role-based authorization checks on the affected endpoint to ensure only users with administrative privileges can access ACL tree structures; validate user roles server-side before returning any ACL data.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MycomplianceofficeApplication
Affected:= 25.3.3.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Mycomplianceoffice installation
    Identify if Mycomplianceoffice is installed in the environment by checking for the application, its web services, or associated processes
    Affected if Mycomplianceoffice is not present in the environment
  2. Check installed product version
    Retrieve the installed version of Mycomplianceoffice. Common methods include: checking the application UI 'About' section, querying the web interface version endpoint, or reviewing installation manifests/logs
    Affected if The installed version matches 25.3.3.1 exactly (note: '=' notation indicates this specific version is affected)
  3. Confirm endpoint existence
    Attempt to access the endpoint /customer/servlet/mco/webapi/admin-view-hierarchy/get-acl-tree-structure via HTTP GET request (requires authentication)
    Affected if The endpoint responds with HTTP 200 or returns any data, indicating it is exposed
  4. Test authorization with low-privilege account
    Authenticate using a non-administrator or low-privileged user account and make a request to the affected endpoint
    Affected if The endpoint returns ACL tree structure data, permission mappings, or RBAC configuration details to the low-privileged user
  5. Inspect response for sensitive data
    Examine the response payload from the endpoint for exposed permission hierarchies, role mappings, or internal access control configuration
    Affected if The response contains administrative-level ACL data, role definitions, or internal RBAC configuration that should be restricted to administrators

The environment is affected if Mycomplianceoffice version 25.3.3.1 is installed AND the /customer/servlet/mco/webapi/admin-view-hierarchy/get-acl-tree-structure endpoint returns ACL tree data to non-administrative users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement role-based authorization checks on the affected endpoint to ensure only users with administrative privileges can access ACL tree structures; validate user roles server-side before returning any ACL data.

Fix this in Mycomplianceoffice Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53905 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53905 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data