Skip to main content

Quest Bot CVE-2026-47188

| EUVDEUVD-2026-36278 LOW
Improper Encoding or Escaping of Output (CWE-116)
2026-06-11 GitHub_M
2.3
CVSS 4.0 · Vendor: GitHub_M
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Attacker holds Discord moderator role
  2. Delivery
    Issues /unban or /unwarn with @everyone in reason field
  3. Exploit
    Bot echoes unsanitized reason to public channel
  4. Execution
    Discord API parses mass mention
  5. Impact
    All guild members receive notification ping

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding for downstream
Exploitation Conditions

Exploitation requires the attacker to hold a Discord role that has been granted permission to use the /unban or /unwarn slash commands within the target guild - this is a non-default permission granted by server administrators, not available to regular members. The bot must be running a version prior to 1.0.5. The mass ping is constrained to the Discord guild where the vulnerable bot is active; it cannot affect users outside that guild. The key limiting factors are: (1) attacker must be a trusted moderator already granted elevated bot command access by server admins; (2) impact is a notification nuisance, not data exfiltration or code execution; (3) no unauthenticated or external attack path exists.

Impact

The CVSS 4.0 base score of 2.3 (Very Low) accurately reflects the constrained real-world impact. The vector AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:L captures key facts: network-reachable but requiring low-privilege (moderator) access; the AT:P (Attack Requirements: Present) metric encodes that the attacker must already possess moderator permissions within the Discord guild, which are granted by server administrators rather than self-assignable. Confidentiality impact is none - no data is disclosed. Integrity and availability impacts are low, limited to unsolicited mass notification delivery (nuisance/disruption). No EPSS score is available in the provided data and no KEV listing exists, consistent with the low exploitability profile. There is no known public exploit code. The primary real-world threat model is a rogue or compromised moderator abusing existing elevated permissions, not an external unauthenticated attacker. The tag 'Information Disclosure' from the NVD appears misapplied - the actual impact is unauthorized notification delivery, not data exposure.

Exploit ScenarioDerived

A Discord server moderator with legitimate access to the /unban and /unwarn commands crafts a reason string containing @everyone such as 'Ban lifted @everyone check pinned rules.' When the bot processes the command and posts the reason in a public channel, the Discord API parses the @everyone mention and delivers a notification to every member of the guild. No public exploit code exists for this vulnerability; the attack requires only knowledge of the flaw and existing moderator permissions.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 11, 2026

Unsanitized reason text in Quest Bot's /unban and /unwarn Discord commands enables authenticated moderators to trigger mass pings against all server members. Versions prior to 1.0.5 of this open-source Discord moderation bot pass user-controlled reason strings directly into public bot messages without setting Discord's allowedMentions restriction, unlike other moderation commands that already suppress mention parsing. An attacker with moderator-level Discord permissions can embed @everyone or @here in any ban or warn reason to force mass notification delivery to all guild members. No active exploitation has been confirmed and no public exploit code has been identified at the time of analysis.

RemediationAI

Vendor-released patch: Quest Bot v1.0.5. Upgrade to version 1.0.5 or later by pulling the latest release from https://github.com/duck-organization/questbot/releases/tag/questbot-v1.0.5, which resolves the missing allowedMentions configuration in the /unban and /unwarn handlers. For operators unable to upgrade immediately, the most effective compensating control is to restrict the Discord role permissions that grant access to /unban and /unwarn to only fully trusted administrators rather than broader moderator groups, thereby reducing the population of principals who can trigger the flaw. Disabling the /unban and /unwarn slash commands entirely in the Discord server configuration is a more disruptive but complete workaround until patching is feasible.

Affected VersionsENISA

quest-bot < 1.0.5

Affected Packages

euvd quest_bot fix: 1.0.5

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Quest Bot (CPE: cpe:2.3:a:duck-organization:quest-bot:*:*:*:*:*:*:*:*) is a Node.js-based Discord bot using the Discord.js library. Discord's API supports an allowedMentions option on message sends that controls which mention types (@everyone, @here, role mentions, user mentions) are parsed and delivered as notifications. The root cause, CWE-116 (Improper Encoding or Escaping of Output), manifests here as inconsistent application of this output control: other moderation commands in the bot already pass allowedMentions restrictions, but the /unban and /unwarn handlers omit the field, allowing the Discord API to parse and deliver all mention types embedded in the reason string. This is a classic output-context encoding failure where user-controlled data is reflected into a notification-capable channel without neutralizing the relevant syntax.

Know when Quest Bot gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitHub_M) PRIMARY 2.3 LOW
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
vuln.today AI 4.3 MEDIUM

Moderator role required (PR:L); no scope change as impact stays within the guild; no confidentiality or meaningful availability impact beyond notification spam.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
4.0 AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

1
Patch available
Jun 11, 2026 - 20:01 EUVD

DescriptionCVE.org

Quest Bot is an opensource modern Discord Bot built for moderation, utilities and support. Prior to version 1.0.5, the latest release suppresses mentions in several moderation commands, but /unban and /unwarn still echo user-controlled reason text in public bot messages without allowedMentions. A moderator can use @everyone or @here in the reason and make the bot send a mass ping. This issue has been patched in version 1.0.5.

Threat Intelligence Overview

EPSS Score
0.0%
Top 87% exploitable
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Low
Technical Impact
Total

Priority Score

12
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +12
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy