{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-39270 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-39270 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-39270 is a medium-severity cross-site scripting vulnerability in discourse DiscoTOC, published on 6 Oct 2022. 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-2022-39270 and fix it if it is affected.\n\nWhat it is: CVE-2022-39270 is a medium-severity cross-site scripting vulnerability in discourse DiscoTOC, published on 6 Oct 2022. 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-2022-39270 in the wild and no public exploit code.\n\nAffected product: discourse DiscoTOC. 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-39270/ (Markdown: https://insights.sbomify.com/CVE-2022-39270/index.md)","id":"CVE-2022-39270","markdown":"https://insights.sbomify.com/CVE-2022-39270/index.md","name":"CVE-2022-39270","record":{"aliases":["GHSA-m44p-w923-w32h"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Discourse theme component","requires_auth":"low_privilege","summary":"Users with sufficient trust levels can inject arbitrary HTML into topic pages via the DiscoTOC component, potentially leading to XSS attacks.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"discotoc","vendor":"discourse"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","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":"DiscoTOC is a Discourse theme component that generates a table of contents for topics. Users that can create topics in TOC-enabled categories (and have sufficient trust level - configured in component's settings) are able to inject arbitrary HTML on that topic's page. The issue has been fixed on the `main` branch. Admins can update the theme component through the admin UI (Customize -\u003e Themes -\u003e Components -\u003e DiscoTOC -\u003e Check for Updates). Alternatively, admins can temporarily disable the DiscoTOC 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 table-of-contents theme component in DiscoTOC","id":"CVE-2022-39270","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Traefik HTTP/2 connections management could cause a denial of service","id":"CVE-2022-39271"},"packages":[],"prev":{"headline":"Media transport downgrade from the secure version (SRTP) to non-secure (RTP) in pjsip","id":"CVE-2022-39269"},"products":["DiscoTOC"],"published":"2022-10-06","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-04-23","vendors":["discourse"]},"summary":"Users with sufficient trust levels can inject arbitrary HTML into topic pages via the DiscoTOC component, potentially leading to XSS attacks.","url":"https://insights.sbomify.com/CVE-2022-39270/"}