{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-43842 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-43842 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-43842 is a medium-severity cross-site scripting vulnerability in Requarks wiki, published on 20 Dec 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-43842 and fix it if it is affected.\n\nWhat it is: CVE-2021-43842 is a medium-severity cross-site scripting vulnerability in Requarks wiki, published on 20 Dec 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-43842 in the wild and no public exploit code.\n\nAffected product: Requarks wiki. 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-2021-43842/ (Markdown: https://insights.sbomify.com/CVE-2021-43842/index.md)","id":"CVE-2021-43842","markdown":"https://insights.sbomify.com/CVE-2021-43842/index.md","name":"CVE-2021-43842","record":{"aliases":["GHSA-3qv4-gp35-rgh7"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Wiki.js","requires_auth":"low_privilege","summary":"A malicious user can execute arbitrary JavaScript in other users' browsers by uploading a crafted SVG file to Wiki.js.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"wiki.js","vendor":"requarks"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Wiki.js is a wiki app built on Node.js. Wiki.js versions 2.5.257 and earlier are vulnerable to stored cross-site scripting through a SVG file upload. By creating a crafted SVG file, a malicious Wiki.js user may stage a stored cross-site scripting attack. This allows the attacker to execute malicious JavaScript when the SVG is viewed directly by other users. Scripts do not execute when loaded inside a page via normal `\u003cimg\u003e` tags. Commit 5d3e81496fba1f0fbd64eeb855f30f69a9040718 fixes this vulnerability by adding an optional (enabled by default) SVG sanitization step to all file uploads that match the SVG mime type. As a workaround, disable file upload for all non-trusted users. Wiki.js version 2.5.260 is the first production version to contain a patch. Version 2.5.258 is the first development build to contain a patch and is available only as a Docker image as requarks/wiki:canary-2.5.258.","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":"Stored XSS via SVG file upload in Wiki.js","id":"CVE-2021-43842","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2021"},"n_packages":0,"n_references":3,"next":{"headline":"Insufficient patch for Regular Expression Denial of Service (ReDoS) to jsx-slack v4.5.1","id":"CVE-2021-43843"},"packages":[],"prev":{"headline":"XSS by SVG upload in xwiki-platform","id":"CVE-2021-43841"},"products":["wiki"],"published":"2021-12-20","related":[{"cvss_score":9.1,"headline":"Security feature bypass in n/a","id":"CVE-2025-56643","kev_date_added":null,"published":"2025-11-18"},{"cvss_score":8.6,"headline":"Wiki.js: Privilege Escalation via Missing Group Validation in users.update","id":"CVE-2026-44224","kev_date_added":null,"published":"2026-05-12"},{"cvss_score":8.6,"headline":"Directory Traversal in Wiki.js","id":"CVE-2020-15236","kev_date_added":null,"published":"2020-10-05"},{"cvss_score":8.2,"headline":"Stored XSS via SVG in Requarks/wiki","id":"CVE-2021-43855","kev_date_added":null,"published":"2021-12-27"},{"cvss_score":8.2,"headline":"Stored XSS in non-image uploads in Requarks/wiki","id":"CVE-2021-43856","kev_date_added":null,"published":"2021-12-27"},{"cvss_score":8.1,"headline":"Improper write access check in Requarks/wiki","id":"CVE-2022-23654","kev_date_added":null,"published":"2022-02-22"},{"cvss_score":7.6,"headline":"XSS in Wiki.js","id":"CVE-2021-21383","kev_date_added":null,"published":"2021-03-18"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["Requarks"]},"summary":"A malicious user can execute arbitrary JavaScript in other users' browsers by uploading a crafted SVG file to Wiki.js.","url":"https://insights.sbomify.com/CVE-2021-43842/"}