# CVE-2026-48485: Quest Bot: Stored warn reasons can still trigger bot-powered mass mentions through `/warns`.

> Attackers can trigger mass mentions by injecting @everyone into stored warning reasons, causing notification spam via the /warns command.

- **Severity:** Low 2.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jun 2026
- **Updated:** 12 Jun 2026
- **Also known as:** GHSA-xjm4-8ggw-8jwf

## What is CVE-2026-48485?

CVE-2026-48485 is a low-severity cross-site scripting vulnerability in duck-organization questbot, published on 12 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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.

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

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


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

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

## Is CVE-2026-48485 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-48485 is a low-severity cross-site scripting vulnerability in duck-organization questbot, published on 12 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48485 exists.

Affected product: duck-organization questbot. 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-48485/ (Markdown: https://insights.sbomify.com/CVE-2026-48485/index.md)
```

## Sources

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

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