CVE-2025-49590
Xwiki Cryptpad ≤ 2025.3.0
Raw vector
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2025-49590 is a low-severity Incomplete Denylist to Cross-Site Scripting (CWE-692) vulnerability in Xwiki Cryptpad. Its CVSS base score is 2.9 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 20th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-18910
Vulnerability Data
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…
more
protocol/scheme is checked, which a maliciously crafted URI can follow. This issue has been patched in version 2025.3.0.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Input validation requires complete, allowlist-style checks that structurally eliminate reliance on incomplete XSS denylists.
Security engineering principles mandate robust sanitization and validation approaches that avoid incomplete denylist patterns.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require robust input validation and sanitization (e.g., allowlists) rather than incomplete denylists for XSS.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can discover incomplete denylists, yet the control does not mandate their replacement.
Secure-SDLC processes encourage proper input/output handling, but do not specifically address denylist shortcomings.
Application-security requirements can mandate proper output encoding, but the control itself does not prescribe the technique.
Secure-coding rules directly require allow-list or context-aware escaping instead of incomplete denylists for XSS.