Quest Bot EUVD-2026-36297

Exploitation requires (1) the attacker already holding the Discord Manage Server / ManageGuild permission in the target guild, (2) Quest Bot version < 1.0.3 installed in that guild, (3) an existing role with the Administrator permission whose hierarchy position is below the Quest Bot's highest role (so the bot is technically able to assign it), and (4) the attacker being able to join the guild with a second controlled account to receive the AutoRole assignment. No end-user interaction from other members is needed, but the attack is blocked entirely if the bot's role is positioned below all Administrator roles, or if the attacker also holds Manage Roles/Administrator (in which case privilege escalation is unnecessary).

The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H, score 7.5) reasonably reflects the realistic risk: network-reachable through Discord, low complexity, but requiring high pre-existing privileges (ManageGuild) and an attack requirement (the bot's role must outrank the targeted admin role). There is no EPSS, KEV, or POC signal in the input - no public exploit identified at time of analysis and no evidence of in-the-wild abuse - so this is a real but bounded risk concentrated to Discord servers using Quest Bot where untrusted moderators hold ManageGuild. The AT:P (attack requirement: present) is the key qualifier defenders should not overlook: if the bot's role is correctly positioned below the Administrator role, exploitation is blocked entirely, so practical impact depends heavily on server-side role configuration discipline.

A semi-trusted moderator who has been granted Manage Server (but intentionally not Manage Roles or Administrator) opens the Quest Bot AutoRole configuration and sets the auto-assigned role to an existing Administrator role that sits below the bot's highest role. The attacker then joins the guild with a controlled alt account, the bot automatically grants it Administrator on join, and the attacker uses that account to take over the server. No public POC is identified, but the advisory describes the steps in enough detail to reproduce.