dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-47169

HIGH · 7.5 CVSS v4.0 Published 2026-06-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Quest Bot is an opensource modern Discord Bot built for moderation, utilities and support. Prior to version 1.0.3, a user with Manage Server / ManageGuild, but without Manage Roles or Administrator, can configure the bot’s AutoRole feature to assign an arbitrary role to new members. If the selected role has Administrator and is below the bot’s highest role, the attacker can join with a controlled account and receive full server admin. This issue has been patched in version 1.0.3.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Quest Bot's AutoRole feature allowed users with only Manage Server permission (without Manage Roles or Administrator) to assign arbitrary roles to new members. When the assigned role had Administrator privileges and was positioned below the bot's highest role, an attacker could join the server with a controlled account and receive full server administrative privileges.

MitigationUpgrade Quest Bot to version 1.0.3 or later, which contains the patch for this authorization bypass vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Quest Bot in the server
    Check the server's bot list or member list for Quest Bot. In Discord, go to Server Settings > Integrations > Bots and Apps to confirm Quest Bot is present.
    Affected if Quest Bot is installed and present in the server.
  2. Determine Quest Bot version
    Use Discord's application menu to view Quest Bot's version info, typically found in the bot's profile or through the bot's own version command if available.
    Affected if The installed version is lower than 1.0.3, or the version cannot be verified.
  3. Verify AutoRole configuration
    Check Quest Bot's settings or configuration for any AutoRole module that assigns roles to new members. This is typically found in the bot's dashboard or through configuration commands.
    Affected if AutoRole feature is enabled and configured to assign roles to new members.
  4. Inspect roles eligible for AutoRole assignment
    Review the server's role list and identify which roles Quest Bot is configured to auto-assign. Check if any of these roles have Administrator permissions enabled.
    Affected if One or more roles with Administrator privileges are configured as auto-assignable roles.
  5. Check role hierarchy positioning
    In Discord Server Settings > Roles, compare the position of Quest Bot's highest role against the admin roles that could be auto-assigned. The bot's role must be higher than any admin role for the vulnerability to be exploitable.
    Affected if Quest Bot's highest role is positioned above any Administrator-privileged role that could be assigned through AutoRole.

A server is affected if Quest Bot version is below 1.0.3, AutoRole is enabled with Administrator-privileged roles, and the bot's role hierarchy allows those admin roles to be assigned to new members.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Quest Bot to version 1.0.3 or later, which contains the patch for this authorization bypass vulnerability.

Recommended fix High confidence

version 1.0.3

  1. Upgrade Quest Bot to version 1.0.3 or later

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47169 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47169 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data