CVE-2026-53903

HIGHNVD 8.18.1
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory published 2026-07-01. NVD baseline CVSS 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

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

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.

CVSS v3
8.1
EG Score
8.1(high)
EG Risk
41(Track)
EG Risk 41/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
15.7%
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-53903(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 61× 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-24 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:19 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:25 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 02:29 UTCEPSS rescore
  10. 2026-07-18 10:04 UTCEPSS rescore
  11. 2026-07-16 22:53 UTCGHSA enrichment
  12. 2026-07-16 17:03 UTCEPSS rescore
  13. 2026-07-16 10:25 UTCGHSA enrichment
  14. 2026-07-15 21:56 UTCGHSA enrichment
  15. 2026-07-15 16:57 UTCEPSS rescore
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 09:27 UTCGHSA enrichment
  18. 2026-07-15 02:00 UTCEPSS rescore
  19. 2026-07-15 02:00 UTCEPSS rescore
  20. 2026-07-14 20:56 UTCGHSA enrichment
  21. 2026-07-14 08:26 UTCGHSA enrichment
  22. 2026-07-13 22:31 UTCEPSS rescore
  23. 2026-07-13 19:57 UTCGHSA enrichment
  24. 2026-07-13 07:28 UTCGHSA enrichment
  25. 2026-07-13 06:13 UTCEPSS rescore
Show 36 more
  1. 2026-07-13 06:13 UTCEPSS rescore
  2. 2026-07-12 18:59 UTCGHSA enrichment
  3. 2026-07-12 06:30 UTCGHSA enrichment
  4. 2026-07-12 05:46 UTCEPSS rescore
  5. 2026-07-11 18:00 UTCGHSA enrichment
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-11 05:31 UTCGHSA enrichment
  9. 2026-07-10 17:02 UTCGHSA enrichment
  10. 2026-07-10 04:33 UTCGHSA enrichment
  11. 2026-07-09 19:10 UTCEPSS rescore
  12. 2026-07-09 19:10 UTCEPSS rescore
  13. 2026-07-09 16:02 UTCGHSA enrichment
  14. 2026-07-09 03:32 UTCGHSA enrichment
  15. 2026-07-08 15:16 UTCEPSS rescore
  16. 2026-07-08 15:16 UTCEPSS rescore
  17. 2026-07-08 15:03 UTCGHSA enrichment
  18. 2026-07-08 02:35 UTCGHSA enrichment
  19. 2026-07-07 14:05 UTCEG score recompute 2.80
  20. 2026-07-07 14:05 UTCGHSA enrichment
  21. 2026-07-07 13:46 UTCEPSS rescore
  22. 2026-07-07 13:46 UTCEPSS rescore
  23. 2026-07-06 18:21 UTCNVD updateCVSS v3 → 8.1 · severity → HIGH
  24. 2026-07-06 16:27 UTCEPSS rescore
  25. 2026-07-06 16:27 UTCEPSS rescore
  26. 2026-07-06 14:03 UTCGHSA enrichment
  27. 2026-07-06 02:23 UTCEPSS rescore
  28. 2026-07-06 02:23 UTCEPSS rescore
  29. 2026-07-05 13:59 UTCGHSA enrichment
  30. 2026-07-05 02:31 UTCEPSS rescore
  31. 2026-07-05 02:30 UTCEPSS rescore
  32. 2026-07-04 13:56 UTCGHSA enrichment
  33. 2026-07-03 13:54 UTCGHSA enrichment
  34. 2026-07-02 13:53 UTCGHSA enrichment
  35. 2026-07-01 13:53 UTCEG score recompute
  36. 2026-07-01 13:52 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-53903?
CVE-2026-53903 is a high vulnerability published on July 1, 2026. 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…
When was CVE-2026-53903 disclosed?
CVE-2026-53903 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-53903 actively exploited?
CVE-2026-53903 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 15.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53903?
CVE-2026-53903 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-53903?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53903, 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-53903

Explore →

Is Your Infrastructure Affected by CVE-2026-53903?

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