dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-47177

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 set the ticket transcript channel to a channel they can read. When tickets are closed, the bot exports the full ticket history and sends it to that configured transcript channel. This can expose private ticket messages to users who could not read the original ticket channel. 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's ticket transcript feature allows users with bot configuration permissions to set any channel they can read as the transcript destination. When tickets are closed, the full ticket history is sent to this channel, exposing private messages to users who could access the transcript channel but not the original ticket channel. This is an information disclosure vulnerability due to insufficient access control validation on the transcript channel selection.

MitigationUpgrade to version 1.0.4. Until patched, restrict who can configure bot settings and audit which channels are configured as transcript destinations.

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 installation
    Locate the bot process or check your bot management system for Quest Bot presence and confirm the running instance
    Affected if Quest Bot is not installed or not in use - the CVE only applies to this specific bot
  2. Check Quest Bot version
    Run the bot's version command, check bot logs on startup, or inspect the bot's package/version file
    Affected if The installed version is earlier than 1.0.4 - versions prior to this patch contain the vulnerability
  3. Verify ticket system is enabled
    Check bot configuration settings for active ticket modules - look for ticket system, transcript features, or support ticket settings
    Affected if Tickets are not configured or the transcript feature is disabled - the vulnerability requires the ticket transcript feature to be active
  4. Inspect transcript destination channel
    Access bot configuration and locate the transcript channel setting within ticket module settings - check which channel ID or name is set as the transcript destination
    Affected if A transcript channel is configured and that channel has different (typically broader) access permissions than the ticket channels themselves
  5. Audit channel permission overlap
    Compare permissions between the configured transcript channel and your ticket channels - determine if users exist who can access the transcript channel but cannot access the original ticket channels
    Affected if Users who cannot see ticket conversations can read the transcript channel - this is the exploitation condition

You are affected if running Quest Bot version below 1.0.4 with ticket transcripts enabled and the transcript channel is accessible to users who lack access to the original ticket 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 to version 1.0.4. Until patched, restrict who can configure bot settings and audit which channels are configured as transcript destinations.

Recommended fix High confidence

version 1.0.4

  1. Identify the current installation method used (e.g., git clone, npm install, Docker)
  2. If using git, navigate to the bot's directory and run 'git fetch' to retrieve the latest changes
  3. Run 'git pull' or 'git checkout v1.0.4' to obtain version 1.0.4
  4. If using a package manager, run 'npm install quest-bot@latest' or the equivalent to update to the latest version
  5. Restart the bot service to apply the changes
  6. Verify the bot is running version 1.0.4 by checking the bot's version command or startup logs

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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