Skip to main content

Quest Bot EUVDEUVD-2026-36274

| CVE-2026-47173 MEDIUM
Improper Encoding or Escaping of Output (CWE-116)
2026-06-11 GitHub_M
6.3
CVSS 4.0 · Vendor: GitHub_M
View

Attack ChainAIDerived

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

  1. Access
    Join target Discord server
  2. Exploit
    Open ticket with @everyone or role mention as reason
  3. Execution
    Bot posts unsanitized reason to ticket channel
  4. Impact
    Discord resolves mention and sends mass notification

Vulnerability Assessment

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

The bot must have been explicitly granted Discord's 'Mention Everyone' permission in the target server - this is an elevated permission not enabled by default in Discord's bot permission model, and without it Discord ignores @everyone and @here in bot-authored messages, fully neutralizing the attack. Any server member with access to the ticket creation command qualifies as an attacker; no elevated role or authentication beyond standard Discord server membership is required (PR:N per CVSS). Exploitation is further limited to Quest Bot versions strictly below 1.0.3. The attack does not work against deployments where 'Mention Everyone' was withheld from the bot, against servers that restrict ticket creation to trusted roles, or against patched instances running version 1.0.3 or later.

Impact

The CVSS 4.0 score of 6.3 (AV:N/AC:L/AT:P/PR:N/UI:N) reflects a medium-severity network-exploitable flaw with no privilege requirement. The AT:P (Attack Target Present) metric is the critical limiting factor: the bot must have been explicitly granted the 'Mention Everyone' Discord permission, which is an elevated, non-default configuration. Without this permission, Discord silently suppresses @everyone and @here in bot messages, rendering the attack ineffective. The impact is bounded to low integrity disruption (VI:L) and low availability disruption (VA:L) - unwanted notification spam - with no confidentiality impact, consistent with the VC:N rating. No EPSS score was provided in the intelligence data, so probabilistic exploitation estimates cannot be made. The vulnerability is absent from CISA KEV and has no known public exploit code, indicating no confirmed active exploitation. Real-world risk is therefore conditional: deployments where Quest Bot was never granted mention permissions are not meaningfully exposed, while those that did grant it face a low-barrier social-engineering or harassment vector. The 'Information Disclosure' tag in the source intelligence appears to be a misclassification - the actual impact is notification abuse, not data leakage.

Exploit ScenarioDerived

A regular Discord server member opens a support ticket and submits '@everyone Bug report' as the ticket reason. Quest Bot, holding the 'Mention Everyone' permission, posts the verbatim reason text into the newly created ticket channel, triggering a mass notification to every user in the server. No exploit tooling or prior privileges are required; the attack requires only a Discord account, server membership, and awareness of the ticket creation command.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.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 output in Quest Bot's ticket creation workflow allows any unprivileged Discord server member to inject @everyone, @here, role mentions, or user mentions into ticket channel messages, causing the bot to trigger mass notifications. All Quest Bot versions prior to 1.0.3 are affected; the bot must hold Discord's 'Mention Everyone' permission for the attack to achieve its full impact. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.

RemediationAI

Upgrade Quest Bot to version 1.0.3, which resolves the output encoding flaw per the vendor security advisory GHSA-27xg-395c-xfcx (https://github.com/duck-organization/questbot/security/advisories/GHSA-27xg-395c-xfcx) and the tagged release at https://github.com/duck-organization/questbot/releases/tag/questbot-v1.0.3. If an immediate upgrade is not possible, revoke the bot's 'Mention Everyone' Discord permission in the server's role settings - this eliminates the exploit's impact entirely, at the cost of preventing any legitimate bot-initiated mass mentions. A secondary compensating control is to restrict ticket creation to trusted or verified roles rather than all server members, which reduces the attacker pool; however, this does not fix the underlying injection flaw and introduces friction for legitimate support workflows. Neither workaround addresses the root CWE-116 defect, so patching remains the definitive remediation.

Affected VersionsENISA

quest-bot < 1.0.3

Affected Packages

euvd quest_bot fix: 1.0.3

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 moderation and support bot (CPE: cpe:2.3:a:duck-organization:quest-bot) that exposes a ticket-creation feature to server members. Discord's message API resolves special mention syntax (@everyone, @here, <@role_id>, <@user_id>) into live notifications when the sending bot token holds the 'Mention Everyone' or appropriate role-mention permission. The root cause is CWE-116 (Improper Encoding or Escaping of Output): the bot accepts free-text ticket reasons from users and relays them verbatim into the resulting ticket channel message without applying Discord's allowed_mentions suppression parameter or stripping mention syntax. A correct implementation would either sanitize user-supplied strings before embedding them in bot messages or set the allowed_mentions field to an empty whitelist, preventing Discord from resolving any mention tokens regardless of bot permissions.

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 6.3 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N
vuln.today AI 4.8 MEDIUM

AC:H reflects that the bot must hold 'Mention Everyone' permission - a non-default server configuration outside attacker control; PR:N as any server member can submit tickets.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
4.0 AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/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
None
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.3, a normal user can create a ticket with a reason containing @everyone, @here, user mentions, or role mentions. When the ticket is created, the bot posts the attacker-controlled reason into the new ticket channel without suppressing mentions. If the bot has permission to use those mentions, the attacker can make the bot ping staff or everyone with access to the ticket channel. This issue has been patched in version 1.0.3.

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 MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.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
Medium
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
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