Approved changes feed: RSS · Atom
cpe:2.3:a:cryptpad:cryptpad:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Cryptpad (45b001e5-3b8c-55ce-b66d-aa0e99a3e699) |
|---|---|
| Product | Cryptpad (31d25418-baac-58f6-aa78-416002aa1c12) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-26028 |
vulnerable | 2026-06-08 07:53:20.740011 |
CryptPad: Sanitizer Bypass in Diffmarked.js Allows Arbitrary HTML Injection and Potential XSS
MEDIUM (6.1)
CryptPad is an end-to-end encrypted collaborative office suite. In versions prior to 2026.2.0, the HTML sanitizer in Diffmarked.js can be bypassed due to incomplete attribute filtering on restricted tags. The sanitizer validates only the src attribute of <iframe>, <video>, and <audio> elements, leaving all other attributes unchecked. As a result, an attacker can inject arbitrary HTML through srcdoc, completely defeating CryptPad's intended bounce sandboxing and enabling link injection or other interactive content within user-controlled documents. The root cause lies in how the sanitizer classifies and enforces tag restrictions: although it defines both forbidden and restricted tag lists, <iframe> is treated as "restricted" rather than "forbidden." Enforcement then inspects only the src attribute, so pairing a benign blob: src with a malicious srcdoc results in unrestricted rendering. This issue has been fixed in version 2026.2.0.
Published: 2026-05-20T18:51:43.643Z
Updated: 2026-05-20T19:33:12.902Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-51846 |
vulnerable | 2026-06-08 07:31:11.310938 |
CryptPad unbounded WebSocket frame flood
HIGH (7.5)
CryptPad 2025.3.1 allows unbounded WebSocket frame flood. A remote, unauthenticated attacker can significantly degrade or deny service for all users of a CryptPad instance. Fixed in 2026.2.2.
Published: 2026-04-30T16:35:59.625Z
Updated: 2026-04-30T17:15:30.109Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-49591 |
vulnerable | 2026-06-08 07:29:13.909848 |
CryptPad 2FA Bypass Vulnerability
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.
Published: 2025-06-18T22:15:16.890Z
Updated: 2025-06-23T16:42:24.165Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-49590 |
vulnerable | 2026-06-08 07:29:13.908108 |
CryptPad Dom-Based Cross-Site Scripting (XSS) Vulnerability
CryptPad is a collaboration suite. Prior to version 2025.3.0, the "Link Bouncer" functionality attempts to filter javascript URIs to prevent Cross-Site Scripting (XSS), however this can be bypassed. There is an "early allow" code path that happens before the URI's protocol/scheme is checked, which a maliciously crafted URI can follow. This issue has been patched in version 2025.3.0.
Published: 2025-06-18T22:14:06.323Z
Updated: 2025-06-23T16:41:36.205Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.