Private-message disclosure via unchecked logging channel
Published Jun 11, 2026 · Updated Jun 11, 2026
Information disclosure in Quest Bot before 1.0.4 allows remote authenticated users to read private-channel message contents through logs. The logging configuration accepts any channel visible to the settings user, and edit and delete handlers copy message content there without checking source-channel visibility. The user needs bot-settings access, such as Manage Server, while the bot can view a private channel and another user edits or deletes a message in it.
Summary
What happened
Information disclosure in Quest Bot before 1.0.4 allows remote authenticated users to read private-channel message contents through logs. The logging configuration accepts any channel visible to the settings user, and edit and delete handlers copy message content there without checking source-channel visibility. The user needs bot-settings access, such as Manage Server, while the bot can view a private channel and another user edits or deletes a message in it.
The record
- CVE
- CVE-2026-47176
- Published
- Jun 11, 2026
- Updated
- Jun 11, 2026
- Vendor
- Vantern
- Product
- Quest Bot
- Classifications
- CWE-200, T1530
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 11, 2026CVE publishedPublication date reported by the CVE source.
- Jun 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.0.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream logging-channel proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo