Quest Bot: Stored warn reasons can still trigger bot-powered mass mentions through `/warns`.
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| duck-organization | questbot | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Duck-organization | Questbot |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.318% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Duck-organization
Duck-organization questbot |
|
| Vendors & Products |
Duck-organization
Duck-organization questbot |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Quest Bot is an opensource Discord Bot. Prior to version 1.1.6, the latest release suppresses mentions when creating, unbanning, unwarning, kicking, muting, and unmuting, but stored warning reasons are still printed by /warns without mention suppression. A moderator can create a warning with @everyone or @here in the reason, then make the bot later output that reason through /warns, causing a mass ping if the bot has permission. This issue has been patched in version 1.1.6. | |
| Title | Quest Bot: Stored warn reasons can still trigger bot-powered mass mentions through `/warns`. | |
| Weaknesses | CWE-116 | |
| References |
| |
| Metrics |
cvssV4_0
|