{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47173 exists.","fix":"No fix has been published for CVE-2026-47173 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-47173 is a medium-severity cross-site scripting vulnerability in duck-organization quest-bot, published on 11 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-47173 and fix it if it is affected.\n\nWhat it is: CVE-2026-47173 is a medium-severity cross-site scripting vulnerability in duck-organization quest-bot, published on 11 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47173 exists.\n\nAffected product: duck-organization quest-bot. 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-2026-47173/ (Markdown: https://insights.sbomify.com/CVE-2026-47173/index.md)","id":"CVE-2026-47173","markdown":"https://insights.sbomify.com/CVE-2026-47173/index.md","name":"CVE-2026-47173","record":{"aliases":["GHSA-27xg-395c-xfcx"],"analysis":{"component_type":"other","fix_type":"upgrade","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Discord moderation bot","requires_auth":"none","summary":"Attackers can inject mentions into ticket reasons, causing the bot to spam notifications to staff or everyone in the channel.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"}],"description":"Quest Bot is an opensource modern Discord Bot built for moderation, utilities and support. Prior to version 1.0.3, a normal user can create a ticket with a reason containing @everyone, @here, user mentions, or role mentions. When the ticket is created, the bot posts the attacker-controlled reason into the new ticket channel without suppressing mentions. If the bot has permission to use those mentions, the attacker can make the bot ping staff or everyone with access to the ticket channel. This issue has been patched in version 1.0.3.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Quest Bot: Ticket reason allows mass-mention injection","id":"CVE-2026-47173","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Duck Site: Untrusted pull request code can trigger privileged production deployment","id":"CVE-2026-47174"},"packages":[],"prev":{"headline":"Quest Bot: Untrusted pull request code can be built and deployed by privileged `workflow_run` deployment.","id":"CVE-2026-47172"},"products":["quest-bot"],"published":"2026-06-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-12","vendors":["duck-organization"]},"summary":"Attackers can inject mentions into ticket reasons, causing the bot to spam notifications to staff or everyone in the channel.","url":"https://insights.sbomify.com/CVE-2026-47173/"}