dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-47197

HIGH · 7.2 CVSS v4.0 Published 2026-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/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 Discord Bot. Prior to version 1.1.6, a moderator with the relevant Discord permission bit can use the bot to moderate users above them in the Discord role hierarchy, as long as the bot itself outranks the target. This bypasses Discord’s normal role hierarchy protections and lets lower-ranked moderators ban, kick, timeout, untimeout, warn, or rename higher-ranked users. This issue has been patched in version 1.1.6.

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 prior to v1.1.6 fails to enforce Discord's role hierarchy in moderation commands. The bot allows any moderator with the relevant permission bit to target users above them in the Discord role hierarchy, provided the bot's role outranks the target user, bypassing Discord's built-in protections against moderating higher-ranked users.

MitigationUpgrade Quest Bot to version 1.1.6 or later, which implements proper role hierarchy validation in moderation actions.

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:H/SA:H/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 installation
    Check your Discord server's installed bots or running processes for Quest Bot. Look in your bot management dashboard, process list, or hosting environment for a bot named 'Quest Bot'
    Affected if Quest Bot is present in the environment
  2. Determine Quest Bot version
    Run the bot's version command (commonly '!version' or '?version' depending on prefix), check bot logs on startup, or query your bot hosting platform for the installed version
    Affected if The installed version is any version prior to v1.1.6 (e.g., v1.1.5, v1.0.0, etc.)
  3. Verify moderation module is active
    Check if Quest Bot has moderation permissions enabled on your server. Review the bot's role permissions in Discord server settings, specifically looking for moderator-level permissions like kick, ban, or warn
    Affected if Moderation commands are enabled and the bot has moderator permissions granted
  4. Confirm bot role position
    In Discord server settings, go to Roles and compare the Quest Bot's role position against other roles. The bot's role must be higher than target users for the vulnerability to be exploitable
    Affected if The Quest Bot's role is positioned above other moderator or user roles in the role hierarchy

You are affected if Quest Bot is running at a version prior to v1.1.6 and has moderation permissions enabled with a role position above other users in your Discord server hierarchy.

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.1.6 or later, which implements proper role hierarchy validation in moderation actions.

Recommended fix Moderate confidence

version 1.1.6

  1. Locate your current Quest Bot installation and identify the running version
  2. Visit the official Quest Bot GitHub repository (check project documentation for the repository URL)
  3. Download or pull the latest release version 1.1.6
  4. Stop the running bot instance
  5. Replace the existing bot files with the new version 1.1.6 files
  6. Restart the bot service
  7. Verify the bot is running version 1.1.6 by checking the bot's version command or startup logs
  8. Test that the role hierarchy enforcement is working correctly by attempting a moderator action on a higher-ranked user (should now be denied)

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
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47197 — 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-47197 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