# CVE-2025-71388: stoatchat 20241213-1 Webhook Token Disclosure via Read Permissions

> Users with read-only permissions can access webhook tokens to send arbitrary messages, bypassing channel restrictions and impersonating bots.

- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/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:** 16 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-8684-rvfj-v3jq, GHSA-9hv3-3cv6-jrx3

## What is CVE-2025-71388?

CVE-2025-71388 is a high-severity missing authorization vulnerability in stoatchat, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

stoatchat (delta/Revolt) versions from 20241213-1 before 20250210-1 allow users with only ViewChannel (read) permission on a channel to fetch that channel's webhooks, including their tokens, because the webhook fetch endpoint checked for ViewChannel instead of ManageWebhooks. Using a retrieved token, an attacker can send arbitrary messages to the channel, bypassing channel permissions and impersonating a bot or webhook. Fixed in 20250210-1 (0.8.2).

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

## Which versions are affected by CVE-2025-71388?


## How do I fix CVE-2025-71388?

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

## Is CVE-2025-71388 being exploited?

There is no known exploitation of CVE-2025-71388 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-71388 and fix it if it is affected.

What it is: CVE-2025-71388 is a high-severity missing authorization vulnerability in stoatchat, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-71388 in the wild and no public exploit code.

Affected product: stoatchat. 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-2025-71388/ (Markdown: https://insights.sbomify.com/CVE-2025-71388/index.md)
```

## Sources

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

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