CVE-2025-49591 Details
Description
CryptPad is a collaboration suite. Prior to version 2025.3.0, enforcement of Two-Factor Authentication (2FA) in CryptPad can be trivially bypassed, due to weak implementation of access controls. An attacker that compromises a user's credentials can gain access to the victim's account, even if the victim has 2FA set up. This is due to 2FA not being enforced if the path parameter is not 44 characters long, which can be bypassed by simply URL encoding a single character in the path. This issue has been patched in version 2025.3.0.
A vulnerability in CryptPad prior to version 2025.3.0 allows for a trivial bypass of Two-Factor Authentication (2FA). This issue arises from a weak implementation of access controls, where 2FA is not enforced if the path parameter is not exactly 44 characters long. An attacker who compromises a user's credentials can access the victim's account, regardless of 2FA being enabled. The vulnerability has been patched in version 2025.3.0.
Users should update to CryptPad version 2025.3.0 or later.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jun 23, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
| CWE-284 | Improper Access Control | [email protected] |
| CWE-287 | Improper Authentication | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| xwiki cryptpad | < 2025.3.0 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Aug 11, 2025 | Reanalysis | [email protected] |
| Aug 11, 2025 | Initial Analysis | [email protected] |
| Jun 18, 2025 | New CVE Received | [email protected] |