Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker holds Discord moderator role
-
DeliveryIssues /unban or /unwarn with @everyone in reason field
-
ExploitBot echoes unsanitized reason to public channel
-
ExecutionDiscord API parses mass mention
-
ImpactAll 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. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – 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
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 (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
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
Moderator role required (PR:L); no scope change as impact stays within the guild; no confidentiality or meaningful availability impact beyond notification spam.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
1DescriptionCVE.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
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.
Privileged GitHub Actions workflow injection in Quest Bot (Discord moderation bot) prior to version 1.0.3 allows remote
Mass mention abuse in Quest Bot (open-source Discord moderation/utility bot) before version 1.0.3 allows any normal Disc
Cross-tenant AutoMod rule deletion in Quest Bot (Discord bot) prior to 1.0.5 lets a user with Manage Server permission i
Privilege escalation in Quest Bot (open-source Discord moderation bot) prior to version 1.0.3 allows a user holding only
Privilege escalation in Quest Bot Discord bot versions prior to 1.0.1 allows any guild member with slash-command access
Unsanitized output in Quest Bot's ticket creation workflow allows any unprivileged Discord server member to inject @ever
Ticket transcript redirection in Quest Bot (prior to v1.0.4) allows a privileged user with bot settings access to config
Quest Bot, an open-source Discord moderation/utility bot, exposes private channel message contents to privileged users w
Quest Bot (Discord moderation bot) prior to v1.0.4 allows low-privileged moderators to leverage the bot's elevated Disco
EUVD-2026-36278
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB