Quick answers
- Is CVE-2026-47173 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47173 being exploited in the wild.
- How severe is CVE-2026-47173?
- Informational severity, with a CVSS score of 6.3, published 11 June 2026.
- Which products and versions are affected?
- Duck-Organization Quest Bot < 1.0.3.
- Is there a fix for CVE-2026-47173?
- A patch was published on 2026-05-17: Version 1.0.3 released and security advisory published on GitHub. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-47173 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-47173?
- Check whether you run Duck-Organization Quest Bot at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Quest Bot prior to version 1.0.3 is vulnerable to a mention injection flaw due to improper encoding or escaping of user-provided output (CWE-116). When a user creates a ticket, the 'reason' provided in the Discord modal is posted by the bot into a new channel without suppressing mentions. An attacker can include payloads such as @everyone, @here, or role IDs (<@&ID>) to force the bot to ping users it has permission to mention. This allows for unauthorized mass notifications and staff harassment. The issue is fixed in version 1.0.3 by ensuring the bot suppresses or escapes mentions in the ticket-opening message.
Affected products
- duck-organization Quest Bot < 1.0.3
Timeline
- 2026-05-17: patched: Version 1.0.3 released and security advisory published on GitHub.
- 2026-06-11: disclosed: CVE-2026-47173 published to the NVD.