EUVD-2026-36415Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessModerator authenticates to Discord server
-
DeliveryIssues /warn command with @everyone embedded in reason text
-
ExploitBot stores unsanitized reason in warning record
-
ExecutionModerator or other user invokes /warns for target
-
PersistBot outputs stored reason without mention encoding
-
ImpactDiscord resolves @everyone ping and notifies all server members
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 two simultaneous conditions: (1) the attacker holds a Discord moderator role within the target server that grants permission to create warnings via Quest Bot's moderation commands, and (2) the bot has been explicitly granted the @everyone or @here guild-level Discord permission by the server owner, which is not a default Discord bot permission. Exploitation is further bounded by needing a subsequent /warns invocation to trigger output - the attacker can either wait for another moderator to run /warns organically or invoke it themselves if they have access. Exploitation is impossible against servers where the bot lacks @everyone/here permission, and against ordinary Discord members who do not hold moderator roles. |
| Impact | The CVSS 4.0 score of 2.1 accurately characterizes this as a low-severity issue. The PR:H metric confirms that exploitation requires Discord moderator-level privileges within the target server - ordinary members cannot create warnings. The AT:P (attack requirements present) metric further narrows exploitability: the bot must have @everyone or @here mention permissions granted by the server owner, which is a non-default, elevated Discord bot permission. Impact is limited to VI:L and VA:L - the primary harm is unauthorized mass notifications disrupting server members, with no confidentiality breach and no persistent system compromise. KEV status is not listed and no public exploit code has been identified. EPSS data is not provided in the source intelligence; given the niche deployment base and high privilege requirement, opportunistic automated exploitation is implausible. This is a real but operationally low-risk issue primarily relevant to Discord communities with strict trust boundaries between bot owners and moderators. |
| Exploit ScenarioDerived | A Discord server moderator with warning permissions crafts a warning for any target user with '@everyone Urgent announcement - click here' embedded in the reason field. Quest Bot stores the reason without stripping the mention. When any moderator subsequently runs /warns for that user, Quest Bot outputs the stored reason verbatim, and Discord resolves @everyone against the bot's guild permissions, triggering a mass notification to all server members. No exploit code is required - the standard bot interface is sufficient. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 12, 2026
Mention injection in Quest Bot prior to version 1.1.6 allows Discord server moderators to embed @everyone or @here mass-ping triggers inside warning reasons, which are later replayed unsanitized when the /warns command outputs stored records. While the bot correctly suppresses Discord mentions during warning creation and several other moderation actions (unbanning, unwarning, kicking, muting, unmuting), the /warns display path lacks equivalent output encoding, creating an inconsistent trust boundary. The issue is patched in version 1.1.6 with no public exploit code identified at time of analysis.
RemediationAI
Vendor-released patch: version 1.1.6. Bot operators should upgrade to questbot-v1.1.6 immediately, available at https://github.com/duck-organization/questbot/releases/tag/questbot-v1.1.6. As a compensating control prior to upgrading, server owners can revoke the bot's @everyone and @here Discord guild permissions, which prevents mass pings even if malicious warning reasons are stored - the trade-off is that any legitimate bot feature relying on those permissions will also be disabled. Alternatively, restricting warning creation to highly trusted moderators reduces the adversarial surface, though this does not eliminate the underlying encoding flaw. Audit existing stored warning reasons for embedded @everyone or @here strings and remove them before the next /warns invocation.
Affected VersionsENISA
Affected Packages
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 is an open-source Discord bot (CPE: cpe:2.3:a:duck-organization:questbot:*:*:*:*:*:*:*:*) that implements Discord moderation commands. Discord bots can trigger mass notifications by including @everyone or @here in message content - provided the bot has been granted the corresponding guild permissions. The root cause is CWE-116 (Improper Encoding or Escaping of Output): mention suppression is applied inconsistently across command handlers. Input-time suppression is implemented for creation and action commands, but the /warns output renderer does not re-encode or strip stored mention strings before relaying them to Discord, violating the principle that output sanitization must occur at every output point regardless of what was done at input time.
Know when Questbot 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
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
Moderator-level privileges required (PR:H); scope unchanged (S:U); only low integrity and availability disruption from mass pings; no confidentiality impact.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
1DescriptionCVE.org
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.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
GitHub
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Improper input validation in Quest Bot (an open-source Discord bot) prior to version 1.1.6 lets a guild moderator weapon
Discord role hierarchy bypass in Quest Bot (open-source Discord moderation bot) prior to version 1.1.6 allows moderators
Authorization bypass in Quest Bot Discord bot prior to version 1.1.6 lets low-privilege guild members invoke the purge a
Ticket panel resource exhaustion in Quest Bot (open-source Discord bot, all versions prior to 1.1.8) allows any Discord
Server-side request forgery in the open-source Discord bot Quest Bot (versions up to and including 1.1.8) lets any ordin
Exploit-DB