Skip to main content

Quest Bot CVE-2026-47196

| EUVDEUVD-2026-36412 HIGH
Improper Input Validation (CWE-20)
2026-06-12 GitHub_M
8.4
CVSS 4.0 · Vendor: GitHub_M
View

Attack ChainAIDerived

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

  1. Access
    Obtain moderator role in target guild
  2. Delivery
    Invoke automod add with whitespace-only input
  3. Exploit
    Bot trims and stores empty rule
  4. Execution
    Members post normal messages
  5. Persist
    Listener evaluates includes("") true
  6. Impact
    Bot deletes every non-bot message

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
Exploitation Conditions

The attacker must already possess privileges sufficient to invoke the Quest Bot automod add slash/text command in the target Discord guild (CVSS PR:L - typically a guild moderator or admin role granted by the server owner), the bot must be running a version prior to 1.1.6 with the automod feature in use, and the payload must be a whitespace-only string so that post-trim storage yields the empty string consumed by the includes("") check. No end-user interaction is required (UI:N) beyond ordinary members posting messages that then get deleted, and exploitation is confined to guilds where the vulnerable bot is installed.

Impact

The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) with high integrity and availability impacts to both vulnerable and subsequent systems yields a score of 8.4, which is plausible: any low-privileged user who can issue the automod add command (typically a server moderator or admin role configured by the guild owner) can permanently disrupt server communication until the bot is removed or the rule is cleared. There is no EPSS, KEV, or SSVC data provided, and no public exploit identified at time of analysis, but the trigger is a single whitespace string so exploitability is effectively trivial once configuration access is obtained. Real-world risk is limited by the small install base typical of niche Discord bots and by the fact that the attacker must already hold privileged automod-configuration rights in the target guild, making this more of a sabotage/insider-misuse risk than a mass-exploitation concern.

Exploit ScenarioDerived

A guild moderator with permission to manage automod rules issues the bot's automod add command with a value consisting solely of spaces; the server trims it to an empty string and stores it as a banned word. From that point onward, every non-bot message posted in the guild matches the empty rule and is deleted by the bot, effectively silencing the channel until an administrator removes the rule or uninstalls the bot.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.1% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Jun 12, 2026

Improper input validation in Quest Bot (an open-source Discord bot) prior to version 1.1.6 lets a guild moderator weaponize the automod feature to delete every non-bot message in a server. By submitting whitespace-only input to the automod add command, the trimmed empty string is stored as a rule and the message listener's content.includes("") check evaluates true for all messages. No public exploit identified at time of analysis, though the trigger is trivial to reproduce by anyone with permission to configure automod rules.

RemediationAI

Vendor-released patch: Quest Bot 1.1.6 - operators running the bot should pull and redeploy this release (see https://github.com/duck-organization/questbot/releases/tag/questbot-v1.1.6 and advisory GHSA-fgwg-6px5-cxp5). If immediate upgrade is not possible, restrict who can invoke the automod add command by tightening Discord role permissions on the bot's configuration commands, and audit the currently configured automod word list to remove any empty or whitespace-only entries; the side effect is that automod rule management becomes limited to a smaller trusted group. As a last-resort containment step, disabling the automod module entirely or removing the bot from the guild will stop the mass-deletion behavior at the cost of losing automated moderation.

Affected VersionsENISA

questbot < 1.1.6

Affected Packages

euvd questbot fix: 1.1.6

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 a Node.js/JavaScript-based Discord bot maintained by the duck-organization GitHub project (CPE: cpe:2.3:a:duck-organization:questbot). The bug is a classic CWE-20 Improper Input Validation: the automod add handler calls String.prototype.trim() on user-supplied banned-word input but never verifies the result is non-empty before persisting it. Downstream, the message listener uses JavaScript's String.prototype.includes() to test whether each guild message contains any stored banned word; per ECMA-262, str.includes("") returns true for every string, so once an empty rule exists the listener flags and deletes every non-bot message regardless of content.

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

Vendor (GitHub_M) PRIMARY 8.4 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:H/SA:H
vuln.today AI 8.1 HIGH

Network-reachable Discord command (AV:N), trivial whitespace payload (AC:L), requires moderator-level automod privileges (PR:L), no user interaction; impact is mass message deletion - high integrity and availability, no confidentiality loss.

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

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

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

Lifecycle Timeline

1
Patch available
Jun 12, 2026 - 14:01 EUVD

DescriptionCVE.org

Quest Bot is an opensource Discord Bot. Prior to version 1.1.6, the automod add command trims user input but does not reject an empty result. Adding a rule containing only whitespace stores an empty word. The message listener later checks content.includes(""), which is always true, causing the bot to delete every non-bot guild message. This issue has been patched in version 1.1.6.

Executive ViewAI

Why It Matters

Quest Bot, an open-source Discord bot used for server management, contains an input validation flaw in its automod feature that allows moderators to delete all non-bot messages by configuring a whitespace-only filter rule. Organizations using versions prior to 1.1.6 face message loss and potential disruption of communication infrastructure. The vulnerability requires only moderator-level permissions and is trivial to exploit without specialized knowledge.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: restrict automod configuration permissions to administrators with demonstrated operational need; implement and monitor Discord audit logs for all automod rule modifications; audit all existing automod rules for suspicious patterns such as whitespace-only or overly-broad matching criteria; disable the automod feature if not critical to operations; evaluate alternative Discord bots with stronger input validation controls.

Threat Intelligence Overview

EPSS Score
0.1%
Top 75% exploitable
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High

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 HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.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
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

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