{"answers":{"affected":"2 open source packages ship an affected version, including mermaid. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54880 exists.","fix":"Upgrade mermaid to 11.10.0 or later.","what":"CVE-2025-54880 is a medium-severity cross-site scripting vulnerability in mermaid-js mermaid, published on 19 Aug 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-54880 and fix it if it is affected.\n\nWhat it is: CVE-2025-54880 is a medium-severity cross-site scripting vulnerability in mermaid-js mermaid, published on 19 Aug 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54880 exists.\n\nAffected packages and fixed versions:\n- mermaid (npm): affected from 11.1.0; fixed in 11.10.0\n- mermaid (npm): affected from 11.1.0; fixed in 11.10.0\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-54880/ (Markdown: https://insights.sbomify.com/CVE-2025-54880/index.md)","id":"CVE-2025-54880","markdown":"https://insights.sbomify.com/CVE-2025-54880/index.md","name":"CVE-2025-54880","record":{"aliases":["GHSA-8gwm-58g9-j8pw","UBUNTU-CVE-2025-54880"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript diagramming library","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary scripts via unsanitized icon text in architecture diagrams, affecting users of the Mermaid JavaScript library.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"mermaid","vendor":"mermaid_project"}],"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:N/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Mermaid is a JavaScript based diagramming and charting tool that uses Markdown-inspired text definitions and a renderer to create and modify complex diagrams. In the default configuration of mermaid 11.9.0 and earlier, user supplied input for architecture diagram icons is passed to the d3 html() method, creating a sink for cross site scripting. This vulnerability is fixed in 11.10.0.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Mermaid does not properly sanitize architecture diagram iconText leading to XSS","id":"CVE-2025-54880","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2025"},"n_packages":2,"n_references":3,"next":{"headline":"Mermaid improperly sanitizes of sequence diagram labels leading to XSS","id":"CVE-2025-54881"},"packages":[{"ecosystem":"npm","fixed":["11.10.0"],"introduced":["11.1.0"],"last_affected":[],"package":"mermaid","purl":null,"source":"GHSA-8gwm-58g9-j8pw"},{"ecosystem":"npm","fixed":["11.10.0"],"introduced":["11.1.0"],"last_affected":[],"package":"mermaid","purl":"pkg:npm/mermaid","source":"GHSA-8gwm-58g9-j8pw"}],"prev":{"headline":"Mastodon e‑mail throttle misconfiguration allows unlimited email confirmations against unconfirmed emails","id":"CVE-2025-54879"},"products":["mermaid"],"published":"2025-08-19","related":[{"cvss_score":7.2,"headline":"Incorrect sanitisation function leads to `XSS`","id":"CVE-2021-43861","kev_date_added":null,"published":"2021-12-30"},{"cvss_score":6.1,"headline":"Cross-site Scripting in Mermaid","id":"CVE-2021-35513","kev_date_added":null,"published":"2021-06-27"},{"cvss_score":5.3,"headline":"Mermaid Gantt Charts are vulnerable to an Infinite Loop DoS","id":"CVE-2026-41150","kev_date_added":null,"published":"2026-05-29"},{"cvss_score":5.3,"headline":"Mermaid: Improper sanitization of configuration leads to CSS injection","id":"CVE-2026-41159","kev_date_added":null,"published":"2026-05-29"},{"cvss_score":4.1,"headline":"Arbitrary `CSS` injection into the generated graph affecting the container HTML in mermaid.js","id":"CVE-2022-31108","kev_date_added":null,"published":"2022-06-28"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-08-19","vendors":["mermaid-js"]},"summary":"Attackers can execute arbitrary scripts via unsanitized icon text in architecture diagrams, affecting users of the Mermaid JavaScript library.","url":"https://insights.sbomify.com/CVE-2025-54880/"}