{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-26287 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-26287 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-26287 is a high-severity cross-site scripting vulnerability in hedgedoc, published on 28 Dec 2020. 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-2020-26287 and fix it if it is affected.\n\nWhat it is: CVE-2020-26287 is a high-severity cross-site scripting vulnerability in hedgedoc, published on 28 Dec 2020. 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-2020-26287 in the wild and no public exploit code.\n\nAffected product: hedgedoc. 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-2020-26287/ (Markdown: https://insights.sbomify.com/CVE-2020-26287/index.md)","id":"CVE-2020-26287","markdown":"https://insights.sbomify.com/CVE-2020-26287/index.md","name":"CVE-2020-26287","record":{"aliases":["GHSA-g6w6-7xf9-m95p"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"HedgeDoc collaborative platform","requires_auth":"low_privilege","summary":"Attackers can inject arbitrary JavaScript via mermaid diagrams in HedgeDoc notes, potentially executing code or taking over accounts.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"hedgedoc","vendor":"hedgedoc"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"HedgeDoc is a collaborative platform for writing and sharing markdown. In HedgeDoc before version 1.7.1 an attacker can inject arbitrary `script` tags in HedgeDoc notes using mermaid diagrams. Our content security policy prevents loading scripts from most locations, but `www.google-analytics.com` is allowed. Using Google Tag Manger it is possible to inject arbitrary JavaScript and execute it on page load. Depending on the configuration of the instance, the attacker may not need authentication to create or edit notes. The problem is patched in HedgeDoc 1.7.1. As a workaround one can disallow `www.google-analytics.com` in the `Content-Security-Policy` header. Note that other ways to leverage the `script` tag injection might exist.","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 in mermaid diagrams","id":"CVE-2020-26287","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2020"},"n_packages":0,"n_references":5,"next":{"headline":"Parse Server stores password in plain text","id":"CVE-2020-26288"},"packages":[],"prev":{"headline":"Arbitary file upload","id":"CVE-2020-26286"},"products":["hedgedoc"],"published":"2020-12-28","related":[{"cvss_score":10,"headline":"PDF export allows arbitrary file reads","id":"CVE-2021-29475","kev_date_added":null,"published":"2021-04-26"},{"cvss_score":8.1,"headline":"XSS vector in slide mode speaker-view","id":"CVE-2021-39175","kev_date_added":null,"published":"2021-08-30"},{"cvss_score":8.1,"headline":"Improper Neutralization of Script-Related HTML Tags in Notes","id":"CVE-2021-29503","kev_date_added":null,"published":"2021-05-19"},{"cvss_score":7.5,"headline":"Arbitary file upload","id":"CVE-2020-26286","kev_date_added":null,"published":"2020-12-28"},{"cvss_score":7.4,"headline":"Stored XSS in slide mode","id":"CVE-2021-21259","kev_date_added":null,"published":"2021-01-22"},{"cvss_score":6.5,"headline":"MySQL \u0026 free URL mode allows to hide existing notes in hedgedoc","id":"CVE-2024-45308","kev_date_added":null,"published":"2024-09-02"}],"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":["hedgedoc"]},"summary":"Attackers can inject arbitrary JavaScript via mermaid diagrams in HedgeDoc notes, potentially executing code or taking over accounts.","url":"https://insights.sbomify.com/CVE-2020-26287/"}