CVE-2026-53902

MEDIUMNVD 6.56.5
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-01. NVD baseline CVSS 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.5
EG Score
6.5(high)
EPSS
15.9%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 6, 2026

Advisory Details (2)

Auto-updated Jul 3, 2026
No patch confirmed yet.
generic

MyComplianceOffice | Compliance Management Software

https://mco.mycomplianceoffice.com/
generic

Vulnerabilities in MyComplianceOffice MCO software | CERT Polska

https://cert.pl/en/posts/2026/07/CVE-2026-53902

Vendor Advisories for CVE-2026-53902(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 33× in last 7d / 33× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 06:20 UTCEG score recompute 0.60
  2. 2026-07-07 06:20 UTCGHSA enrichment
  3. 2026-07-06 18:21 UTCNVD updateCVSS v3 → 6.5 · severity → MEDIUM
  4. 2026-07-06 17:56 UTCEG score recompute
  5. 2026-07-06 17:56 UTCGHSA enrichment
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 16:27 UTCEPSS rescore
  8. 2026-07-06 05:31 UTCEG score recompute
  9. 2026-07-06 05:31 UTCGHSA enrichment
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-06 02:23 UTCEPSS rescore
  12. 2026-07-05 17:08 UTCEG score recompute
  13. 2026-07-05 17:08 UTCGHSA enrichment
  14. 2026-07-05 04:45 UTCEG score recompute
  15. 2026-07-05 04:45 UTCGHSA enrichment
  16. 2026-07-05 02:31 UTCEPSS rescore
  17. 2026-07-05 02:30 UTCEPSS rescore
  18. 2026-07-04 16:16 UTCEG score recompute
  19. 2026-07-04 16:16 UTCGHSA enrichment
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-04 06:31 UTCEPSS rescore
  22. 2026-07-04 03:52 UTCEG score recompute
  23. 2026-07-04 03:52 UTCGHSA enrichment
  24. 2026-07-03 15:28 UTCEG score recompute
  25. 2026-07-03 15:28 UTCGHSA enrichment
Show 8 more
  1. 2026-07-03 03:05 UTCEG score recompute
  2. 2026-07-03 03:05 UTCGHSA enrichment
  3. 2026-07-02 14:40 UTCEG score recompute
  4. 2026-07-02 14:40 UTCGHSA enrichment
  5. 2026-07-02 02:16 UTCEG score recompute
  6. 2026-07-02 02:16 UTCGHSA enrichment
  7. 2026-07-01 13:53 UTCEG score recompute
  8. 2026-07-01 13:52 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-53902?
CVE-2026-53902 is a medium vulnerability published on July 1, 2026. 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…
When was CVE-2026-53902 disclosed?
CVE-2026-53902 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53902 actively exploited?
CVE-2026-53902 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 15.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53902?
CVE-2026-53902 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-53902?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53902, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53902

Explore →

Is Your Infrastructure Affected by CVE-2026-53902?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.