{"answers":{"affected":"4 open source packages ship an affected version, including @seafile/sdoc-editor. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-30587 in the wild and no public exploit code.","fix":"Upgrade @seafile/sdoc-editor to a fixed version for your release line: 2.0.209 or 3.0.75.","what":"CVE-2026-30587 is a medium-severity cross-site scripting vulnerability in n/a, published on 25 Mar 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-30587 and fix it if it is affected.\n\nWhat it is: CVE-2026-30587 is a medium-severity cross-site scripting vulnerability in n/a, published on 25 Mar 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-30587 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @seafile/sdoc-editor (npm): affected all versions; fixed in 2.0.209\n- @seafile/sdoc-editor (npm): affected all versions; fixed in 2.0.209\n- @seafile/sdoc-editor (npm): affected from 3.0.0; fixed in 3.0.75\n- @seafile/sdoc-editor (npm): affected from 3.0.0; fixed in 3.0.75\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-30587/ (Markdown: https://insights.sbomify.com/CVE-2026-30587/index.md)","id":"CVE-2026-30587","markdown":"https://insights.sbomify.com/CVE-2026-30587/index.md","name":"CVE-2026-30587","record":{"aliases":["GHSA-rqj3-x344-qvxc"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Seafile Server","requires_auth":"low_privilege","summary":"Authenticated attackers can inject malicious JavaScript via unsanitized WebSocket messages in the Seadoc editor, potentially leading to code execution or account takeover.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"seafile_server","vendor":"seafile"}],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","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":"Multiple Stored XSS vulnerabilities exist in Seafile Server version 13.0.15,13.0.16-pro,12.0.14 and prior and fixed in 13.0.17, 13.0.17-pro, and 12.0.20-pro, via the Seadoc (sdoc) editor. The application fails to properly sanitize WebSocket messages regarding document structure updates. This allows authenticated remote attackers to inject malicious JavaScript payloads via the src attribute of embedded Excalidraw whiteboards or the href attribute of anchor tags","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Seafile Server has multiple stored XSS vulnerabilities","id":"CVE-2026-30587","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2026"},"n_packages":4,"n_references":6,"next":{"headline":"Code injection in n/a","id":"CVE-2026-30603"},"packages":[{"ecosystem":"npm","fixed":["2.0.209"],"introduced":["0"],"last_affected":[],"package":"@seafile/sdoc-editor","purl":null,"source":"GHSA-rqj3-x344-qvxc"},{"ecosystem":"npm","fixed":["2.0.209"],"introduced":["0"],"last_affected":[],"package":"@seafile/sdoc-editor","purl":"pkg:npm/%40seafile/sdoc-editor","source":"GHSA-rqj3-x344-qvxc"},{"ecosystem":"npm","fixed":["3.0.75"],"introduced":["3.0.0"],"last_affected":[],"package":"@seafile/sdoc-editor","purl":null,"source":"GHSA-rqj3-x344-qvxc"},{"ecosystem":"npm","fixed":["3.0.75"],"introduced":["3.0.0"],"last_affected":[],"package":"@seafile/sdoc-editor","purl":"pkg:npm/%40seafile/sdoc-editor","source":"GHSA-rqj3-x344-qvxc"}],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2026-30586"},"products":["n/a"],"published":"2026-03-25","related":[{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2014-5443","kev_date_added":null,"published":"2018-03-19"},{"cvss_score":7.4,"headline":"Permissions check bypass in Seafile","id":"CVE-2021-43820","kev_date_added":null,"published":"2021-12-14"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2025-65516","kev_date_added":null,"published":"2025-12-04"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"2026-05-10","vendors":["n/a"]},"summary":"Authenticated attackers can inject malicious JavaScript via unsanitized WebSocket messages in the Seadoc editor, potentially leading to code execution or account takeover.","url":"https://insights.sbomify.com/CVE-2026-30587/"}