{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-22213 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-22213 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-22213 is a cross-site scripting vulnerability in nextcloud security-advisories, published on 18 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-22213 and fix it if it is affected.\n\nWhat it is: CVE-2024-22213 is a cross-site scripting vulnerability in nextcloud security-advisories, published on 18 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-22213 in the wild and no public exploit code.\n\nAffected product: nextcloud security-advisories. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-22213/ (Markdown: https://insights.sbomify.com/CVE-2024-22213/index.md)","id":"CVE-2024-22213","markdown":"https://insights.sbomify.com/CVE-2024-22213/index.md","name":"CVE-2024-22213","record":{"aliases":["GHSA-mg7w-x9fm-9wwc"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Nextcloud Deck app","requires_auth":"low_privilege","summary":"Attackers can execute malicious code in victims' browsers by sending crafted HTML comments in the Nextcloud Deck application.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"deck","vendor":"nextcloud"}],"cvss":{"score":0,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Cross-site Scripting when sending HTML as a comment in the Nextcloud Deck app","id":"CVE-2024-22213","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Missing authorization in n/a","id":"CVE-2024-22216"},"packages":[],"prev":{"headline":"Nextcloud global site selector authentication bypass","id":"CVE-2024-22212"},"products":["security-advisories"],"published":"2024-01-18","related":[{"cvss_score":8.1,"headline":"Missing permission check on Deck API","id":"CVE-2021-39225","kev_date_added":null,"published":"2021-10-25"},{"cvss_score":8,"headline":"Missing authorization in Nextcloud Deck","id":"CVE-2020-8182","kev_date_added":null,"published":"2020-10-05"},{"cvss_score":6.5,"headline":"Circle can be accessed by non-Circle members in Nextcloud Deck","id":"CVE-2021-37631","kev_date_added":null,"published":"2021-09-07"},{"cvss_score":6.5,"headline":"Information disclosure in Nextcloud Deck","id":"CVE-2021-22913","kev_date_added":null,"published":"2021-06-11"},{"cvss_score":5.8,"headline":"Nextcloud Deck card vulnerable to data leak to unauthorized users via reference preview cache","id":"CVE-2023-22469","kev_date_added":null,"published":"2023-01-10"},{"cvss_score":5.4,"headline":"Nextcloud Deck app allowed user with \"Can share\" permission to modify permissions of other non-owners","id":"CVE-2025-66557","kev_date_added":null,"published":"2025-12-05"},{"cvss_score":5,"headline":"Possibility for anyone to add a stack with existing tasks on anyone's board in Nextcloud Deck","id":"CVE-2022-29159","kev_date_added":null,"published":"2022-05-20"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-11-13","vendors":["nextcloud"]},"summary":"Attackers can execute malicious code in victims' browsers by sending crafted HTML comments in the Nextcloud Deck application.","url":"https://insights.sbomify.com/CVE-2024-22213/"}