{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-46180 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-46180 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-46180 is a medium-severity cross-site scripting vulnerability in discourse-mermaid-theme-component, published on 4 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-46180 and fix it if it is affected.\n\nWhat it is: CVE-2022-46180 is a medium-severity cross-site scripting vulnerability in discourse-mermaid-theme-component, published on 4 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-46180 in the wild and no public exploit code.\n\nAffected product: discourse-mermaid-theme-component. 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-2022-46180/ (Markdown: https://insights.sbomify.com/CVE-2022-46180/index.md)","id":"CVE-2022-46180","markdown":"https://insights.sbomify.com/CVE-2022-46180/index.md","name":"CVE-2022-46180","record":{"aliases":["GHSA-8437-hgcm-p3q3"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Discourse theme component","requires_auth":"low_privilege","summary":"Attackers can inject arbitrary HTML into posts via the Discourse Mermaid theme component, potentially leading to script execution or account takeover.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"mermaid","vendor":"discourse"}],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"Discourse Mermaid (discourse-mermaid-theme-component) allows users of Discourse, open-source forum software, to create graphs using the Mermaid syntax. Users of discourse-mermaid-theme-component version 1.0.0 who can create posts are able to inject arbitrary HTML on that post. The issue has been fixed on the `main` branch of the GitHub repository, with 1.1.0 named as a patched version. Admins can update the theme component through the admin UI. As a workaround, admins can temporarily disable discourse-mermaid-theme-component.","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":"Arbitrary HTML injection in discourse-mermaid-theme-component","id":"CVE-2022-46180","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Gotify server XSS vulnerability in the application image file upload","id":"CVE-2022-46181"},"packages":[],"prev":{"headline":"LiuOS vulnerable to Authorization Bypass through User-Controlled Key","id":"CVE-2022-46179"},"products":["discourse-mermaid-theme-component"],"published":"2023-01-04","related":[],"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-03-10","vendors":["discourse"]},"summary":"Attackers can inject arbitrary HTML into posts via the Discourse Mermaid theme component, potentially leading to script execution or account takeover.","url":"https://insights.sbomify.com/CVE-2022-46180/"}