# CVE-2026-47189: Quest Bot: AutoMod removal can delete rules from another guild by global rule ID

> Attackers can delete AutoMod rules from other guilds by exploiting missing ownership checks during rule removal.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jun 2026
- **Updated:** 11 Jun 2026
- **Also known as:** GHSA-6rv9-6p24-w955

## What is CVE-2026-47189?

CVE-2026-47189 is a high-severity missing authorization vulnerability in duck-organization quest-bot, published on 11 Jun 2026. An attacker can exploit it over the internet without logging in, 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 AutoMod remove flow looks up and deletes rules by global database ID without verifying that the rule belongs to the guild where the command is executed. A user can learn a victim guild’s AutoMod rule ID through autocomplete, then remove that rule from another guild where they have Manage Server. This issue has been patched in version 1.0.5.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-47189 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47189 is a high-severity missing authorization vulnerability in duck-organization quest-bot, published on 11 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47189 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-47189/ (Markdown: https://insights.sbomify.com/CVE-2026-47189/index.md)
```

## Sources

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

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