Questbot
Monthly
Discord role hierarchy bypass in Quest Bot (open-source Discord moderation bot) prior to version 1.1.6 allows moderators to perform privileged actions against users ranked above them in the server role hierarchy. Any moderator holding the relevant Discord permission bit can ban, kick, timeout, untimeout, warn, or rename higher-ranked members so long as the bot itself outranks the target. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV.
Authorization bypass in Quest Bot Discord bot prior to version 1.1.6 lets low-privilege guild members invoke the purge and slowmode commands in channels where their channel-level permissions explicitly deny moderation. The bot only validates guild-wide permissions on the invoking member and ignores Discord's per-channel permission overrides, so a user excluded from moderating a specific channel can still delete messages and alter slowmode there. No public exploit identified at time of analysis, and the issue is patched in v1.1.6.
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.
Server-side request forgery in the open-source Discord bot Quest Bot (versions up to and including 1.1.8) lets any ordinary member of a server the bot has joined drive the bot's 'image to GIF' command against HTTPS services bound to loopback or internal addresses. The command accepts a user-supplied URL, and the helper that is supposed to block internal destinations validates one DNS answer but then re-resolves the hostname when the request is actually sent, so an attacker who controls a domain with a short TTL can answer public during validation and internal during connection (DNS rebinding, CWE-918). Impact is deliberately narrow: the request is pinned to HTTPS on port 443 and content is only returned when the response is a genuine image, so the realistic outcome is blind internal probing with limited retrieval of image responses, not arbitrary data disclosure, and plain-HTTP cloud metadata services are not reachable by this path; severity is low (CVSS 4.0 score 2.3, assessed CVSS 3.1 AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N) and the priority label is 'monitor'. The advisory publishes PoC reproduction steps (a loopback-only HTTPS server, a rebinding domain, and repeated command invocations), though no packaged working exploit is confirmed; the flaw is fixed in 1.1.9, and there is no KEV listing or evidence of active exploitation.
Ticket panel resource exhaustion in Quest Bot (open-source Discord bot, all versions prior to 1.1.8) allows any Discord user with panel access to flood a server with unlimited ticket channels and database records. Each modal submission unconditionally spawns a new Discord channel and database entry with no duplicate-ticket check and no rate limiting, enabling trivial availability denial of the ticketing system. No active exploitation (KEV) or public exploit code has been identified; vendor-released patch version 1.1.8 is confirmed available.
Mention injection in Quest Bot prior to version 1.1.6 allows Discord server moderators to embed @everyone or @here mass-ping triggers inside warning reasons, which are later replayed unsanitized when the /warns command outputs stored records. While the bot correctly suppresses Discord mentions during warning creation and several other moderation actions (unbanning, unwarning, kicking, muting, unmuting), the /warns display path lacks equivalent output encoding, creating an inconsistent trust boundary. The issue is patched in version 1.1.6 with no public exploit code identified at time of analysis.
Discord role hierarchy bypass in Quest Bot (open-source Discord moderation bot) prior to version 1.1.6 allows moderators to perform privileged actions against users ranked above them in the server role hierarchy. Any moderator holding the relevant Discord permission bit can ban, kick, timeout, untimeout, warn, or rename higher-ranked members so long as the bot itself outranks the target. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV.
Authorization bypass in Quest Bot Discord bot prior to version 1.1.6 lets low-privilege guild members invoke the purge and slowmode commands in channels where their channel-level permissions explicitly deny moderation. The bot only validates guild-wide permissions on the invoking member and ignores Discord's per-channel permission overrides, so a user excluded from moderating a specific channel can still delete messages and alter slowmode there. No public exploit identified at time of analysis, and the issue is patched in v1.1.6.
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.
Server-side request forgery in the open-source Discord bot Quest Bot (versions up to and including 1.1.8) lets any ordinary member of a server the bot has joined drive the bot's 'image to GIF' command against HTTPS services bound to loopback or internal addresses. The command accepts a user-supplied URL, and the helper that is supposed to block internal destinations validates one DNS answer but then re-resolves the hostname when the request is actually sent, so an attacker who controls a domain with a short TTL can answer public during validation and internal during connection (DNS rebinding, CWE-918). Impact is deliberately narrow: the request is pinned to HTTPS on port 443 and content is only returned when the response is a genuine image, so the realistic outcome is blind internal probing with limited retrieval of image responses, not arbitrary data disclosure, and plain-HTTP cloud metadata services are not reachable by this path; severity is low (CVSS 4.0 score 2.3, assessed CVSS 3.1 AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N) and the priority label is 'monitor'. The advisory publishes PoC reproduction steps (a loopback-only HTTPS server, a rebinding domain, and repeated command invocations), though no packaged working exploit is confirmed; the flaw is fixed in 1.1.9, and there is no KEV listing or evidence of active exploitation.
Ticket panel resource exhaustion in Quest Bot (open-source Discord bot, all versions prior to 1.1.8) allows any Discord user with panel access to flood a server with unlimited ticket channels and database records. Each modal submission unconditionally spawns a new Discord channel and database entry with no duplicate-ticket check and no rate limiting, enabling trivial availability denial of the ticketing system. No active exploitation (KEV) or public exploit code has been identified; vendor-released patch version 1.1.8 is confirmed available.
Mention injection in Quest Bot prior to version 1.1.6 allows Discord server moderators to embed @everyone or @here mass-ping triggers inside warning reasons, which are later replayed unsanitized when the /warns command outputs stored records. While the bot correctly suppresses Discord mentions during warning creation and several other moderation actions (unbanning, unwarning, kicking, muting, unmuting), the /warns display path lacks equivalent output encoding, creating an inconsistent trust boundary. The issue is patched in version 1.1.6 with no public exploit code identified at time of analysis.