MyComplianceOffice MCO 25.3.3.1 Password Reset excessive authentication

Summaryinfo

A vulnerability marked as problematic has been reported in MyComplianceOffice MCO 25.3.3.1. This impacts an unknown function of the component Password Reset Handler. This manipulation causes excessive authentication. This vulnerability is registered as CVE-2026-53904. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in MyComplianceOffice MCO 25.3.3.1. It has been declared as problematic. Affected by this vulnerability is an unknown code of the component Password Reset Handler. The manipulation with an unknown input leads to a excessive authentication vulnerability. The CWE definition for the vulnerability is CWE-307. The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, making it more susceptible to brute force attacks. As an impact it is known to affect confidentiality. The summary by CVE is:

MCO is vulnerable to Account Denial of Service due to improper implementation of password reset functionality. Each password reset request invalidates previously set password as well as previously issued temporary passwords, furthermore, password resets are not limited in any way. An attacker who provides victim's email and answer to their security question, can successfully initiate the reset process and continuously invalidate credentials, effectively locking the victim out of their account. Answering security questions has a limited number of tries which lowers the risk of this vulnerability. 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 published with AFINE Team. The advisory is shared at cert.pl. This vulnerability is known as CVE-2026-53904 since 06/11/2026. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1110.001 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