dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-47195

HIGH · 7.1 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 →
77/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, the purge and slowmode commands check only guild-level permissions on the invoking member. They do not check the member’s effective permissions in the channel where the command is run. A user denied channel-level moderation permissions can still delete messages or change slowmode through the bot. 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 versions prior to 1.1.6 contain an authorization bypass vulnerability in the purge and slowmode commands. These commands verify only guild-level permissions on the invoking member while ignoring channel-specific permission overwrites, allowing users denied channel-level moderation permissions to still delete messages or modify slowmode settings through the bot.

MitigationUpgrade Quest Bot to version 1.1.6 or later, which includes the proper channel-level permission checks.

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:L/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 and version
    Locate the Quest Bot instance (check bot hosting environment, configuration files, or run a version command if available). Compare the installed version to 1.1.6 - any version prior to 1.1.6 is affected.
    Affected if Installed Quest Bot version is below 1.1.6
  2. Confirm presence of purge command
    Check if the Quest Bot has the purge or message deletion command enabled in your Discord server. Consult the bot's command list or help documentation.
    Affected if Quest Bot is running below version 1.1.6 AND the purge command is enabled in the server
  3. Confirm presence of slowmode command
    Check if the Quest Bot has the slowmode command enabled in your Discord server. Consult the bot's command list or help documentation.
    Affected if Quest Bot is running below version 1.1.6 AND the slowmode command is enabled in the server
  4. Verify channel-level permission configuration
    In Discord server settings, navigate to channel permission settings. Identify any channel-specific permission overwrites that deny specific users or roles the 'Manage Messages' or 'Slowmode' permissions.
    Affected if Channel-level permission overwrites exist that deny moderation permissions to users or roles, AND Quest Bot version is below 1.1.6
  5. Test command execution with restricted permissions
    As a user who has guild-level moderation permissions but is denied channel-level 'Manage Messages' or slowmode permissions via channel overwrites, attempt to invoke the purge or slowmode command through Quest Bot.
    Affected if The user can successfully execute purge or slowmode commands despite having channel-level permission denials - this confirms the vulnerability is exploitable

You are affected if Quest Bot version is below 1.1.6 AND channel-specific permission overwrites are in place that deny users moderation permissions, yet those users can still successfully use the bot's purge or slowmode commands.

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 includes the proper channel-level permission checks.

Recommended fix High confidence

1.1.6

  1. 1. Identify the current version of Quest Bot deployed in your environment
  2. 2. If the version is prior to 1.1.6, obtain and install version 1.1.6 or later from the official GitHub repository
  3. 3. After upgrading, verify that the purge and slowmode commands now correctly enforce channel-level permission checks in addition to guild-level permissions
  4. 4. Test that users denied channel-level moderation permissions can no longer delete messages or change slowmode through the bot

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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