Typebot CVE-2026-39966

Exploitation requires a valid authenticated Typebot session with at least low-privilege access (PR:L per CVSS vector - a regular user account with no special roles). The attacker must know or successfully enumerate the target bot's ID, which is referenced in a Typebot Link block within a bot they control. The vulnerability is triggered via the getLinkedTypebots API endpoint, which is part of the builder application's logic-block feature set. No special server-side configuration is required - the flawed code path is active by default in all 3.15.2 deployments. Exploitation is limited to read-only access (C:H/I:N/A:N); an attacker cannot modify or delete bots through this vector. The requirement for an authenticated account limits mass anonymous exploitation, but any registered Typebot user - including those on free tiers - meets the prerequisite.

The CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N scores 6.5, reflecting network-reachable, low-complexity exploitation requiring only a low-privilege authenticated account with no user interaction. The high confidentiality impact rating is fully justified given that leaked bot definitions may contain hardcoded API keys, credentials, and PII - secrets that are frequently reusable across other systems. EPSS data was not provided in the source intelligence, so exploitation probability cannot be quantified from that signal. This CVE is not listed in CISA KEV, and no standalone public exploit code has been identified, making exploitation status 'no public exploit identified at time of analysis.' However, the low attack complexity - any authenticated user, no special tooling, just a crafted API call with a target bot ID - means exploitation is trivially automatable once a bot ID is known or enumerated. The gap between CVSS 6.5 and actual risk is meaningful: the real-world priority should be treated as higher than medium due to potential credential exposure. No conflicting signals between CVSS vector and description - both consistently indicate a low-privilege, network-accessible exploit path.

An attacker with a free or low-privilege Typebot account creates a bot containing a Typebot Link block configured with the ID of a target private bot in another workspace - the bot ID may be obtained through enumeration, social engineering, or prior reconnaissance. The attacker then triggers the getLinkedTypebots API call, which returns the full bot definition including all embedded variables, webhook URLs, and integration API keys. Because no public exploit code has been identified, exploitation currently requires manual construction of the API call, but the low complexity makes scripted mass-enumeration straightforward for a motivated attacker.