What is the CVSS score of CVE-2026-48759?

CVE-2026-48759 has a CVSS 3.1 base score of 7.1 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L. EPSS exploitation probability: 0.2%.

Which versions of Typebot are affected by CVE-2026-48759?

Typebot 3.15.2 and earlier contains a cross-workspace tampering vulnerability allowing any authenticated workspace member to modify or delete theme templates belonging to other workspaces, creating…

How to fix or mitigate CVE-2026-48759?

Within 24 hours: Inventory all Typebot instances and document current versions deployed. Within 7 days: Upgrade all instances to Typebot 3.16.0 or later and validate deployment in staging before production rollout. Within 30 days: Review audit logs for unauthorized theme template modifications during the vulnerability window (retroactive detection); implement role-based access controls to restrict workspace member permissions where operationally feasible.

Typebot CVE-2026-48759

HIGH

Authorization Bypass Through User-Controlled Key (CWE-639)

2026-06-17 GitHub_M

Authentication Bypass Typebot Io Baptistearno

7.1

CVSS 3.1 · Vendor: GitHub_M

Severity by source

Vendor (GitHub_M) PRIMARY

7.1 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L

vuln.today AI

7.1 HIGH

Network-reachable API, trivial request crafting, requires any low-priv non-guest workspace member (PR:L), no UI, high integrity from arbitrary template overwrite, low availability from deletion, no confidentiality impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

Low

Lifecycle Timeline

Source Code Evidence Fetched

Jun 17, 2026 - 23:01 vuln.today

Analysis Generated

Jun 17, 2026 - 23:01 vuln.today

DescriptionCVE.org

TypeBot is a chatbot builder tool. Versions 3.15.2 and below have an Insecure Direct Object Reference vulnerability through cross-workspace Theme Template modification and deletion. The handleSaveThemeTemplate and handleDeleteThemeTemplate handlers validate that the authenticated user is a non-guest member of the provided workspaceId, but then operate on themeTemplateId via Prisma queries that do NOT include workspaceId in the WHERE clause. This allows any authenticated user to modify or delete theme templates belonging to any other workspace and may expose Template IDs via shared typebots or network traffic. This issue has been fixed in version 3.16.0.

AnalysisAI

Cross-workspace tampering in Typebot 3.15.2 and earlier allows any authenticated workspace member to modify or delete theme templates belonging to other workspaces by supplying a foreign themeTemplateId to the handleSaveThemeTemplate and handleDeleteThemeTemplate handlers. The handlers verify only that the caller is a non-guest member of the workspaceId argument but execute Prisma queries that omit workspaceId from the WHERE clause, producing an Insecure Direct Object Reference (CWE-639). No public exploit identified at time of analysis, and the issue was remediated in Typebot 3.16.0.

Technical ContextAI

Typebot.io is an open-source chatbot builder by baptisteArno (CPE cpe:2.3:a:baptistearno:typebot.io) that uses a multi-tenant workspace model where users belong to workspaces and templates/typebots are scoped to a workspaceId. The vulnerability is an authorization-check / data-access mismatch: the API authorizes the caller against the workspaceId parameter sent by the client, but the underlying Prisma update/delete query keys solely on themeTemplateId without re-binding to that workspace. This is the textbook CWE-639 (Authorization Bypass Through User-Controlled Key) pattern - the trust boundary is checked on one identifier while the database operation is performed on another. Theme Template IDs can leak through shared typebots or network traffic, removing the practical secrecy that might otherwise have served as an implicit access control.

RemediationAI

Vendor-released patch: Typebot 3.16.0 - upgrade self-hosted deployments to v3.16.0 or later (https://github.com/baptisteArno/typebot.io/releases/tag/v3.16.0) and consult GHSA-qv4p-4mp3-pvpv (https://github.com/baptisteArno/typebot.io/security/advisories/GHSA-qv4p-4mp3-pvpv) for advisory details. If immediate upgrade is not possible, a targeted workaround is to patch the handleSaveThemeTemplate and handleDeleteThemeTemplate handlers to include workspaceId in the Prisma WHERE clause (e.g., where: { id: themeTemplateId, workspaceId }) so the authorization check and database key match; this is a small local code change with no user-facing side effects. As a coarser compensating control, restrict workspace membership to trusted users and disable open self-signup on shared instances until patched, accepting the trade-off of reduced onboarding flow. Audit theme templates after upgrade to detect any prior tampering or unexpected deletions, since the bug leaves no native audit trail.