# CVE-2026-47188: Quest Bot: Unban and unwarn reason fields still allow bot-powered mass mentions.

> Attackers can trigger mass mentions via unban/unwarn reason fields, causing notification spam and potential service disruption.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jun 2026
- **Updated:** 13 Jun 2026
- **Also known as:** GHSA-r978-qqg9-vvxw

## What is CVE-2026-47188?

CVE-2026-47188 is a low-severity vulnerability in duck-organization quest-bot, published on 11 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Quest Bot is an opensource modern Discord Bot built for moderation, utilities and support. Prior to version 1.0.5, the latest release suppresses mentions in several moderation commands, but /unban and /unwarn still echo user-controlled reason text in public bot messages without allowedMentions. A moderator can use @everyone or @here in the reason and make the bot send a mass ping. This issue has been patched in version 1.0.5.

Weakness: CWE-116 (Improper Encoding or Escaping of Output)

## Which versions are affected by CVE-2026-47188?


## How do I fix CVE-2026-47188?

No fix has been published for CVE-2026-47188 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-47188 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47188 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47188 and fix it if it is affected.

What it is: CVE-2026-47188 is a low-severity vulnerability in duck-organization quest-bot, published on 11 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47188 exists.

Affected product: duck-organization quest-bot. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47188/ (Markdown: https://insights.sbomify.com/CVE-2026-47188/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47188
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47188
- OSV: https://osv.dev/vulnerability/CVE-2026-47188

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47188/
Summaries are generated and may contain mistakes; the official description above is the record.