Skip to main content
VulnerabilityPublished

CVE-2026-48485: duck-organization questbot · Improper Encoding or Escaping of Output

Affects duck-organization questbotSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.1 Low : upgrade to 1.1.6 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 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 30 Oct 2026.

What to do

Upgrade questbot and duck-organization/questbot to 1.1.6.

Affected software

ProductAffectedFixed in
duck-organizationquestbotAffected
  • <1.1.6
Fixed in
  • 1.1.6
GitHubduck-organization/questbotpkg:github/duck-organization/questbotOther threatsAffected
  • <1.1.6
Fixed in
  • 1.1.6

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.1.6 or later, where mention suppression in warning reasons output has been implemented. No other mitigation is necessary as the issue is fixed in this version.

Description

Quest Bot is an opensource Discord Bot. Prior to version 1.1.6, the latest release suppresses mentions when creating, unbanning, unwarning, kicking, muting, and unmuting, but stored warning reasons are still printed by /warns without mention suppression. A moderator can create a warning with @everyone or @here in the reason, then make the bot later output that reason through /warns, causing a mass ping if the bot has permission. This issue has been patched in version 1.1.6.

References

Community reviews

Loading reviews…