dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-47176

MEDIUM · 5.7 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 →
61/100
Remediation priority · Elevated
Remotely reachable

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.4, a user who can configure bot settings can enable logging and choose a logging channel they can read. The bot then logs deleted and edited message contents from every channel it can see, including private channels the configuring user cannot access. This issue has been patched in version 1.0.4.

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 before version 1.0.4 contains an authorization bypass vulnerability in its message logging feature. Users with bot configuration permissions can enable message logging and select a channel they can read. The bot then logs all deleted and edited message contents from every channel it can access, including private channels the configuring user cannot access, leading to information disclosure of private communications.

MitigationUpgrade Quest Bot to version 1.0.4 or later. Additionally, restrict bot configuration permissions to trusted administrators only and audit existing logging configurations for unauthorized access to private channel content.

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
P
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:H/VI:N/VA:N/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
    Run the bot with a version flag (such as --version) or use a bot info command to retrieve the installed version number
    Affected if The version is lower than 1.0.4 (for example, 1.0.3, 1.0.2, etc.)
  2. Determine if message logging feature is enabled
    Inspect the bot's configuration settings or database for the message logging feature toggle; look for any enabled flag related to deleted/edited message logging
    Affected if Message logging is turned on
  3. Identify channels configured for message logging
    Review the logging configuration to see which channel(s) are set as the destination for logged messages
    Affected if A logging destination channel exists in the configuration
  4. Check bot permissions in private channels
    Review the bot's channel permissions to determine which private channels the bot has access to (including reading message content)
    Affected if The bot has read access to any private or restricted channels that the configuring user cannot access
  5. Assess user access to logging destination
    Verify whether the user who enabled message logging has read access to the designated logging channel
    Affected if The configuring user can read the logging channel but the bot logs content from private channels they cannot access

You are affected if Quest Bot version is below 1.0.4, message logging is enabled, and the bot has access to private channels while the logging output is visible to a user who cannot see those private channels.

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.4 or later. Additionally, restrict bot configuration permissions to trusted administrators only and audit existing logging configurations for unauthorized access to private channel content.

Recommended fix High confidence

1.0.4

  1. 1. Identify the current version of Quest Bot running in your environment
  2. 2. If running a version prior to 1.0.4, stop the bot service
  3. 3. Update the bot to version 1.0.4 or later
  4. 4. Restart the bot service
  5. 5. Verify the bot is running version 1.0.4 or later

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
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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