dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-47189

HIGH · 8.3 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 →
92/100
Remediation priority · Urgent
Remotely reachable No privileges 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.5, the AutoMod remove flow looks up and deletes rules by global database ID without verifying that the rule belongs to the guild where the command is executed. A user can learn a victim guild’s AutoMod rule ID through autocomplete, then remove that rule from another guild where they have Manage Server. This issue has been patched in version 1.0.5.

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

This is an Insecure Direct Object Reference (IDOR) vulnerability in Quest Bot's AutoMod rule removal feature. The bot uses a global database ID to identify and delete AutoMod rules but fails to verify that the rule belongs to the specific guild where the command is executed. An attacker with Manage Server permissions in one guild can discover another guild's AutoMod rule IDs via autocomplete functionality and then delete those rules from their own guild, causing denial of AutoMod protection in the victim guild.

MitigationUpgrade Quest Bot to version 1.0.5 or later, which implements proper guild ownership verification before allowing AutoMod rule deletion.

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

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/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 version
    Use Discord commands to check the bot's version (such as /botinfo or /version), or check the bot's documentation/status message. Compare the version number to 1.0.5.
    Affected if The installed Quest Bot version is below 1.0.5
  2. Verify AutoMod rules exist in your guild
    Run /automod rules list or navigate to Server Settings > AutoMod in your Discord server to list configured AutoMod rules.
    Affected if Your guild has one or more AutoMod rules configured and the Quest Bot version is below 1.0.5
  3. Confirm autocomplete functionality is available
    In Discord, type the Quest Bot command for managing AutoMod rules (such as /automod delete) and observe if autocomplete suggests rule IDs without requiring guild verification.
    Affected if Autocomplete shows rule IDs from other guilds or allows rule ID input without validating guild ownership, and the bot version is below 1.0.5
  4. Check for cross-guild rule manipulation capability
    Attempt to delete an AutoMod rule using its ID via Quest Bot commands while verifying the rule belongs to your guild by checking the rule list.
    Affected if The bot accepts and processes rule deletion commands without confirming the rule belongs to the guild issuing the command, indicating missing ownership verification.

Your environment is affected if Quest Bot version is below 1.0.5 and your guild has configured AutoMod rules, because the bot lacks guild ownership verification before allowing rule deletion.

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.5 or later, which implements proper guild ownership verification before allowing AutoMod rule deletion.

Recommended fix High confidence

version 1.0.5

  1. Upgrade Quest Bot to version 1.0.5 or later

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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