# CVE-2025-64706: Typebot IDOR Vulnerability: Unauthorized API Token Deletion and Exposure

> An authenticated attacker can delete and retrieve any user's API tokens by manipulating IDs, bypassing authorization checks in Typebot.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 13 Nov 2025
- **Updated:** 13 Nov 2025
- **Also known as:** GHSA-grx8-g27p-8hpp

## What is CVE-2025-64706?

CVE-2025-64706 is a medium-severity missing authorization vulnerability in baptisteArno typebot.io, published on 13 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Typebot is an open-source chatbot builder. In version 3.9.0 up to but excluding version 3.13.0, an Insecure Direct Object Reference (IDOR) vulnerability exists in the API token management endpoint. An authenticated attacker can delete any user's API token and retrieve its value by simply knowing the target user's ID and token ID, without requiring authorization checks. Version 3.13.0 fixes the issue.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Typebot Typebot.

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

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

## Is CVE-2025-64706 being exploited?

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

## Other vulnerabilities in baptisteArno typebot.io

- [CVE-2025-64709](https://insights.sbomify.com/CVE-2025-64709/): Typebot May Expose AWS EKS Credentials via Server Side Request Forgery in Webhook Block (critical 9.6)
- [CVE-2024-30264](https://insights.sbomify.com/CVE-2024-30264/): typebot.io: `GHSL-2024-040` (high 8.1)
- [CVE-2025-65098](https://insights.sbomify.com/CVE-2025-65098/): Typebot Vulnerable to Credential Theft via Client-Side Script Execution and API Authorization Bypass (high 7.4)
- [CVE-2021-24902](https://insights.sbomify.com/CVE-2021-24902/): Typebot < 1.4.3 - Admin+ Stored Cross Site Scripting (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-64706 is a medium-severity missing authorization vulnerability in baptisteArno typebot.io, published on 13 Nov 2025. 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-2025-64706 exists.

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

## Sources

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

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