{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-58487 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-58487 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-58487 is a medium-severity cross-site scripting vulnerability in hedgedoc, published on 13 Jul 2026. 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-2026-58487 and fix it if it is affected.\n\nWhat it is: CVE-2026-58487 is a medium-severity cross-site scripting vulnerability in hedgedoc, published on 13 Jul 2026. 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-2026-58487 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-2026-58487/ (Markdown: https://insights.sbomify.com/CVE-2026-58487/index.md)","id":"CVE-2026-58487","markdown":"https://insights.sbomify.com/CVE-2026-58487/index.md","name":"CVE-2026-58487","record":{"aliases":["GHSA-6c2w-8w96-3pcv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"HedgeDoc notes application","requires_auth":"low_privilege","summary":"Attackers can inject arbitrary HTML into HedgeDoc pages via crafted email addresses, altering content and embedding malicious resources for other users.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"}],"description":"HedgeDoc is an open source, real-time, collaborative, markdown notes application. Prior to version 1.11.0, due to unsafe handling of the local-part of registered email addresses, HedgeDoc was vulnerable to stored HTML Injection through its publish and slide views. An attacker could register a specially crafted email address and inject arbitrary HTML into pages viewed by other users. HedgeDoc  accepted RFC 5321 quoted-string local-parts in email addresses during registration. The local-part was then reused as the user's display name without escaping and rendered into HTML in multiple places, including publish and slide views as well as the collaborative editor. An attacker could break out of an HTML attribute and inject arbitrary markup into the page. While the deployed Content-Security-Policy prevented straightforward inline JavaScript execution, the injected HTML was still sufficient to alter page content and embed attacker-controlled resources such as cross-origin iframes. This issue was fixed in version 1.11.0.","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: Stored HTML injection via email local-part","id":"CVE-2026-58487","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"HedgeDoc: Rate-limit bypass via CF-Connecting-IP header spoofing","id":"CVE-2026-58488"},"packages":[],"prev":{"headline":"HedgeDoc: Denial-of-service via YAML alias expansion in note frontmatter","id":"CVE-2026-58486"},"products":["hedgedoc"],"published":"2026-07-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"2026-07-15","vendors":["hedgedoc"]},"summary":"Attackers can inject arbitrary HTML into HedgeDoc pages via crafted email addresses, altering content and embedding malicious resources for other users.","url":"https://insights.sbomify.com/CVE-2026-58487/"}