CVE-2026-47702

TypeBot API tokens stored in plaintext

Published Aug 11, 2026 CVSS 4.0 · 9.1 Critical EPSS < 1% KEV · Not listed
Description
TypeBot is a chatbot builder tool. In version 3.16.1, API tokens (bearer credentials used to authenticate against the builder API) are stored in the database as cleartext strings. An attacker who gains read access to the database (e.g., via SQL injection, backup exposure, or insider access) can extract all API tokens and impersonate any user without requiring a password or multi-factor authentication. Version 3.17.0 fixes the issue.

Analysis

AI-generated

Technical impact

TypeBot stores bearer credentials in the database as cleartext strings in version 3.16.1. An attacker who can read the database, such as through SQL injection, a leaked backup, or insider privilege, can extract every API token. These tokens grant full API access without requiring a password or multi‑factor authentication, enabling the attacker to impersonate any user, modify data, or perform any action the user is authorized to do. This vulnerability is a classic credentials‑compromise flaw (CWE‑312).

Affected Systems

The flaw exists in TypeBot version 3.16.1 from the vendor baptisteArno:typebot.io. Versions 3.17.0 and later contain the fix, while earlier releases are not affected.

Risk and Exploitability

The CVSS score of 9.1 classifies the issue as critical. EPSS information is not available and the vulnerability is not listed in the CISA KEV catalog, but the lack of protection for stored credentials remains a high‑risk scenario. The likely attack vector requires only database read access, which can be achieved via SQL injection, exposed backups, or privileged insiders. Once tokens are exfiltrated, the attacker immediately gains full API access, effectively bypassing all authentication mechanisms.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade TypeBot to version 3.17.0 or a later release that removes plaintext token storage.
  • Revoke and regenerate any API tokens that were issued by affected versions, and notify all users to update their tokens.
  • Restrict database access to the minimum necessary privilege set, enable encryption at rest, and review audit logs for suspicious token reads.

Generated by OpenCVE AI on August 11, 2026 at 23:26 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Baptistearno
Baptistearno typebot.io
Vendors & Products Baptistearno
Baptistearno typebot.io
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description TypeBot is a chatbot builder tool. In version 3.16.1, API tokens (bearer credentials used to authenticate against the builder API) are stored in the database as cleartext strings. An attacker who gains read access to the database (e.g., via SQL injection, backup exposure, or insider access) can extract all API tokens and impersonate any user without requiring a password or multi-factor authentication. Version 3.17.0 fixes the issue.
Title TypeBot API tokens stored in plaintext
Weaknesses CWE-312
References
Metrics cvssV4_0

{'score': 9.1, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-312

    Cleartext Storage of Sensitive Information

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 11, 2026, 2:46 PM
Reserved
May 19, 2026, 9:18 PM
Status
Deferred
Published
Aug 11, 2026, 3:17 PM
Modified
Oct 23, 2026, 7:10 PM