Skip to main content
VulnerabilityPublished

CVE-2025-64706: baptisteArno typebot.io · Insecure Direct Object Reference

Affects baptisteArno typebot.ioSource CVE Database V5

0

Not known to be exploited · CVSS 5.0 Medium : upgrade to 3.13.0 when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
5.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.13.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade baptistearno/typebot.io to 3.13.0.

Affected software

ProductAffectedFixed in
GitHubbaptistearno/typebot.iopkg:github/baptistearno/typebot.ioOther threatsAffected
  • <3.13.0 >=3.9.0
Fixed in
  • 3.13.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Upgrade all instances of typebot.io to version 3.13.0 or later, where the vulnerability is patched.
  2. Implement strict role-based access controls (RBAC) to limit which users can manage API tokens, minimizing the number of accounts with token management privileges.
  3. Monitor API token management endpoints for unusual activity, such as deletion or retrieval requests from unexpected user accounts or IP addresses.
  4. Enforce multi-factor authentication (MFA) for all users with access to token management features to reduce the risk of compromised credentials.
  5. Conduct regular audits of API tokens and their usage to detect anomalies or unauthorized access.
  6. If upgrading immediately is not feasible, consider implementing compensating controls such as network segmentation or API gateway filtering to restrict access to token management endpoints.
  7. Educate developers and administrators about the importance of authorization checks and secure API design to prevent similar vulnerabilities.

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.

References

Community reviews

Loading reviews…