Skip to main content
VulnerabilityPublished

CVE-2026-53907: MyComplianceOffice MCO · XSS or 'Cross-site Scripting'

Affects MyComplianceOffice MCOSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.8 Medium.

Data as of 14 Nov 2026, 20:44 UTC

CVSS 4.0 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
MyComplianceOfficeMCOAffected
  • =25.3.3.1
Fixed in–

AI-suggested

Since the vendor has not responded to contact attempts, users should restrict permissions to change the application logo to trusted administrators only and monitor for suspicious SVG uploads.

Description

MCO is vulnerable to Stored Cross‑Site Scripting (XSS) via the application logo upload functionality. An attacker with the ability to change the application logo can upload a crafted SVG file containing malicious JavaScript code that is executed when the logo is rendered or opened. Because vendor contact attempts were unsuccessful, the vulnerability has only been confirmed in version 25.3.3.1 but may also affect other versions.

References

Community reviews

Loading reviews…