{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-39279 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-39279 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-39279 is a medium-severity cross-site scripting vulnerability in discourse-chat, published on 6 Oct 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-39279 and fix it if it is affected.\n\nWhat it is: CVE-2022-39279 is a medium-severity cross-site scripting vulnerability in discourse-chat, published on 6 Oct 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-39279 in the wild and no public exploit code.\n\nAffected product: discourse-chat. 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-39279/ (Markdown: https://insights.sbomify.com/CVE-2022-39279/index.md)","id":"CVE-2022-39279","markdown":"https://insights.sbomify.com/CVE-2022-39279/index.md","name":"CVE-2022-39279","record":{"aliases":["GHSA-qp62-8m3c-9jgj"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Discourse chat plugin","requires_auth":"high_privilege","summary":"Staff members can execute arbitrary scripts via XSS in chat channel names and descriptions, requiring an upgrade to the Discourse-chat plugin.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"discourse-chat","vendor":"discourse"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"discourse-chat is a plugin for the Discourse message board which adds chat functionality. In versions prior to 0.9 some places render a chat channel's name and description in an unsafe way, allowing staff members to cause an cross site scripting (XSS) attack by inserting unsafe HTML into them. Version 0.9 has addressed this issue. Users are advised to upgrade. There are no known workarounds for this issue.","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":"Discourse-chat plugin susceptible to XSS in channel name and description","id":"CVE-2022-39279","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Regular expression denial of service in dparse","id":"CVE-2022-39280"},"packages":[],"prev":{"headline":"Istio vulnerable to denial of service attack due to Golang Regex Library","id":"CVE-2022-39278"},"products":["discourse-chat"],"published":"2022-10-06","related":[{"cvss_score":5.4,"headline":"Discourse-Chat Cross-Site Scripting issue for channel names and descriptions","id":"CVE-2022-36057","kev_date_added":null,"published":"2022-09-06"},{"cvss_score":4.3,"headline":"Exposure of Sensitive Information in discourse-chat","id":"CVE-2022-31095","kev_date_added":null,"published":"2022-06-21"}],"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":"Staff members can execute arbitrary scripts via XSS in chat channel names and descriptions, requiring an upgrade to the Discourse-chat plugin.","url":"https://insights.sbomify.com/CVE-2022-39279/"}