CVE-2024-22213 json
Cross-site Scripting when sending HTML as a comment in the Nextcloud Deck app
published 2024-01-18 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-19789
- cvss
- 0.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 43%
- public exploits
- 0
- none known
Summary
Deck is a kanban style organization tool aimed at personal planning and project organization for teams integrated with Nextcloud. In affected versions users could be tricked into executing malicious code that would execute in their browser via HTML sent as a comment. It is recommended that the Nextcloud Deck is upgraded to version 1.9.5 or 1.11.2. There are no known workarounds for this vulnerability.
Patch / fix
- nextcloud deck 1.9.5, 1.11.2
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 23 mo ago
Exploit prediction
0.51% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/nextcloud/security-advisories/security/advisories/GHSA-mg7w-x9fm-9wwc referenced PoC, tagged "exploit" by a source, unverified
- hackerone.com https://hackerone.com/reports/2058556 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 0.0 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:N |
| NVD | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
Affected products
- nextcloud security-advisories
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/nextcloud/deck/commit/91f1557362047f8840f53151f176b80148650bcd
patch
-
github.com
/nextcloud/security-advisories/security/advisories/GHSA-mg7w-x9fm-9wwc
exploit, patch, vendor-advisory
-
hackerone.com
/reports/2058556
exploit, issue-tracking, third-party-advisory
Sources
- CVE List CVE-2024-22213
- NVD CVE-2024-22213
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.