Quest Bot CVE-2026-47189

Requires that (1) the attacker and the victim guild both use the same Quest Bot instance prior to 1.0.5, (2) the attacker holds Discord Manage Server permission in at least one guild where the bot is present so the AutoMod commands are authorized to them, and (3) the attacker uses the bot's AutoMod rule autocomplete to discover the victim guild's global rule ID. Exploitation is limited by the requirement for Manage Server in some guild, by the need to share a bot instance with the target, and by the impact being scoped to AutoMod rule deletion (integrity/availability of moderation config) rather than arbitrary bot or Discord takeover.

The CVSS 4.0 vector AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:H scores 8.3 (High), reflecting unauthenticated network reachability and high integrity/availability impact on a victim guild's moderation rules, with AT:P acknowledging the attacker must control a guild where they hold Manage Server. PR:N is technically defensible because no Discord-level authentication is required by the bot itself, but realistically the attacker must be a Manage Server admin in some guild and must enumerate the victim rule ID via autocomplete - a meaningful barrier the raw score understates. No EPSS, KEV listing, or public POC is present in the supplied data, so this is a credible integrity/availability risk for any server running an unpatched Quest Bot instance, but it is not evidence of mass exploitation; the practical priority is moderate-to-high for active Quest Bot deployments and low for the general internet.

An attacker who owns or controls a Discord guild where Quest Bot is installed grants themselves Manage Server, then uses the bot's AutoMod remove command autocomplete to enumerate rule IDs belonging to an unrelated victim guild that shares the same bot instance. They then invoke the remove command with the harvested global ID, and the bot deletes the victim guild's AutoMod rule without verifying ownership, silently degrading the victim's moderation posture. No public POC has been published, but the issue is straightforward to reproduce from the advisory description.