Skip to main content
VulnerabilityPublished Updated

CVE-2026-47175: duck-organization quest-bot · Improper Encoding or Escaping of Output

Affects duck-organization quest-botSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.3 Low : upgrade to 1.0.4 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.0.4
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade quest-bot and duck-organization/questbot to 1.0.4.

Affected software

ProductAffectedFixed in
duck-organizationquest-botAffected
  • <1.0.4
Fixed in
  • 1.0.4
GitHubduck-organization/questbotpkg:github/duck-organization/questbotOther threatsAffected
  • <1.0.4
Fixed in
  • 1.0.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade quest-bot to version 1.0.4 or later, where this issue has been fixed. No other mitigation is required as the patch addresses the improper mention parsing.

Description

Quest Bot is an opensource modern Discord Bot built for moderation, utilities and support. Prior to version 1.0.4, several moderation commands echo user-controlled reason text in public bot replies without disabling mention parsing. A moderator who does not have permission to mention everyone can still make the bot send @everyone or @here if the bot has that permission. This issue has been patched in version 1.0.4.

References

Community reviews

Loading reviews…