CVE-2026-47189

Vulnerability

In Quest Bot versions prior to 1.0.5, the AutoMod remove command (/automod remove) deletes rules by their global database ID without verifying that the rule belongs to the guild where the command is executed. The vulnerable code is in apps/bot/src/commands/moderation/automod.ts (functions autocompleteRun and chatInputRun) and apps/bot/src/lib/automod.ts (functions getAutoMod and removeAutoMod). The autocomplete handler returns rule IDs for the current guild without checking Manage Server permission, and the remove handler only checks caller permissions in the command's guild, then deletes the rule without comparing autoMod.guildId to interaction.guildId. [1][2]

Exploitation

An attacker must have the bot installed in both a victim guild (where they are a normal member) and an attacker guild (where they have Manage Server permission). First, in the victim guild, the attacker runs /automod remove word: and triggers autocomplete to obtain a victim rule ID from the response. Then, in the attacker guild, they run /automod remove word:<victim_rule_id>. Because the removal logic does not scope deletion to the command's guild, the victim guild's rule is deleted. [2]

Impact

Successful exploitation allows an attacker to delete AutoMod blocked-word rules from a guild where they are only a normal member. This weakens the victim guild's moderation capabilities by removing configured AutoMod rules, potentially enabling disruptive or malicious content to bypass automated filters. [2]

Mitigation

The vulnerability is patched in version 1.0.5 of Quest Bot. Users should update to the latest release (tagged questbot-v1.0.5). No workarounds are documented. The fix ensures that the AutoMod removal handler verifies the rule belongs to the guild where the command is executed. [1][2]