{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-32391 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-32391 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-32391 is a medium-severity cross-site scripting vulnerability in hedgedoc, published on 10 Apr 2025. 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-2025-32391 and fix it if it is affected.\n\nWhat it is: CVE-2025-32391 is a medium-severity cross-site scripting vulnerability in hedgedoc, published on 10 Apr 2025. 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-2025-32391 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-2025-32391/ (Markdown: https://insights.sbomify.com/CVE-2025-32391/index.md)","id":"CVE-2025-32391","markdown":"https://insights.sbomify.com/CVE-2025-32391/index.md","name":"CVE-2025-32391","record":{"aliases":["GHSA-3983-rrqh-mvx5"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"HedgeDoc notes application","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary scripts via malicious SVG uploads in HedgeDoc, potentially compromising user accounts.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"hedgedoc","vendor":"hedgedoc"}],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/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 an open source, real-time, collaborative, markdown notes application. Prior to 1.10.3, a malicious SVG file uploaded to HedgeDoc results in the possibility of XSS when opened in a new tab instead of the editor itself. The XSS is possible by exploiting the JSONP capabilities of GitHub Gist embeddings. Only instances with the local filesystem upload backend or special configurations, where the uploads are served from the same domain as HedgeDoc, are vulnerable. This vulnerability is fixed in 1.10.3. When upgrading to HedgeDoc 1.10.3 is not possible, instance owners could add the following headers for all routes under /uploads as a first-countermeasure: Content-Disposition: attachment and Content-Security-Policy: default-src 'none'. Additionally, the external URLs in the script-src attribute of the Content-Security-Policy header should be removed.","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":"HedgeDoc allows XSS possibility through malicious SVG uploads","id":"CVE-2025-32391","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"AutoGPT has a DoS vulnerability in LoopVideoBlock","id":"CVE-2025-32392"},"packages":[],"prev":{"headline":"EspoCRM vulnerable to HTML Injection into phishing, which may lead to account takeover","id":"CVE-2025-32390"},"products":["hedgedoc"],"published":"2025-04-10","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.7,"headline":"Stored XSS in mermaid diagrams","id":"CVE-2020-26287","kev_date_added":null,"published":"2020-12-28"},{"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-10","vendors":["hedgedoc"]},"summary":"Attackers can execute arbitrary scripts via malicious SVG uploads in HedgeDoc, potentially compromising user accounts.","url":"https://insights.sbomify.com/CVE-2025-32391/"}