MyComplianceOffice MCO 25.3.3.1 SVG File cross site scripting

Summaryinfo

A vulnerability was found in MyComplianceOffice MCO 25.3.3.1. It has been classified as problematic. The affected element is an unknown function of the component SVG File Handler. Performing a manipulation results in cross site scripting. This vulnerability was named CVE-2026-53907. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in MyComplianceOffice MCO 25.3.3.1. It has been classified as problematic. This affects an unknown code block of the component SVG File Handler. The manipulation with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity. The summary by CVE is:

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.

The weakness was presented with AFINE Team. The advisory is shared at cert.pl. This vulnerability is uniquely identified as CVE-2026-53907 since 06/11/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Additional levels of successful authentication are necessary for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• MyComplianceOffice

Name

• MCO

Version

• 25.3.3.1

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion