CVE-2026-48759: TypeBot IDOR Vulnerability in Theme Template Access (v3.15.2 & Below)

Technical summary

CVE-2026-48759 is an Insecure Direct Object Reference (IDOR) vulnerability affecting TypeBot versions 3.15.2 and below. The vulnerable code paths are in the handleSaveThemeTemplate and handleDeleteThemeTemplate handlers. During request processing, the application correctly validates that the authenticated user holds a non-guest role within the specified workspaceId. However, the subsequent Prisma ORM queries that retrieve and modify theme templates omit workspaceId from their WHERE clauses, creating a direct object reference vulnerability. This allows any authenticated user to operate on themeTemplateId values from arbitrary workspaces. Template IDs may also be exposed through shared typebots or network observation, enabling reconnaissance. The vulnerability was resolved in version 3.16.0 by adding proper workspace scoping to the database queries.

Business impact

An attacker exploiting this flaw can corrupt or destroy theme templates across other organizations' TypeBot instances without authorization. This translates to service disruption for end users of affected chatbots, potential reputational damage, and loss of design work. Multi-tenant TypeBot deployments face heightened risk if customers share template IDs through integrations or public links. Attackers could also use template modification as a pivot point to inject malicious content into chatbot conversations, indirectly affecting downstream users or customers interacting with compromised bots.

Affected systems

TypeBot versions 3.15.2 and earlier are vulnerable. The vulnerability applies to any deployment where multiple workspaces exist and users are authenticated. Self-hosted TypeBot instances and cloud-hosted SaaS deployments are equally affected. Upgrading to version 3.16.0 or later resolves the issue.

Exploitability

This vulnerability requires only basic authentication—an attacker needs valid TypeBot credentials but need not be a member of the target workspace. No additional complexity is introduced by network position (directly internet-accessible), user interaction, or privilege escalation; the attack is straightforward once an authenticated session is established. Template IDs can be discovered through shared typebots, publicly visible configurations, or enumeration. The CVSS score of 7.1 (HIGH) reflects the combination of low attack complexity and high integrity impact, though confidentiality remains unaffected and availability is only partially impacted (specific templates, not the entire service).

Remediation

Upgrade TypeBot to version 3.16.0 or later. Organizations running 3.15.2 or below should prioritize this update to prevent unauthorized template modification and deletion. If immediate patching is not feasible, implement network-level controls to restrict TypeBot API access to trusted internal networks or IP ranges, though this is not a substitute for patching.

Patch guidance

TypeBot version 3.16.0 contains the fix. Verify the version number in your deployment by checking the package metadata or admin interface. Apply the update through your standard deployment mechanism (package manager, container image pull, or manual binary replacement). Test the update in a staging environment first to confirm no custom integrations or workflows are disrupted. After patching, confirm that theme template operations are scoped correctly and cross-workspace access is blocked.

Detection guidance

Monitor for suspicious patterns in API access logs: repeated or unusual calls to /api/*/themes or /api/*/templates endpoints from a single user account targeting multiple workspaceIds in a short timeframe, especially followed by DELETE or PUT operations. Log all handleSaveThemeTemplate and handleDeleteThemeTemplate invocations with their workspaceId and themeTemplateId parameters; compare the workspace ownership of the template against the authenticated user's workspace membership. Implement alerting for any template modification or deletion originating from a user not explicitly assigned to that workspace. If you have TypeBot application logs, search for template operations with mismatched workspace contexts.

Why prioritize this

This vulnerability merits urgent attention because it enables any authenticated user to sabotage or alter core design assets of other organizations within a multi-tenant environment. The attack requires no privilege escalation, no social engineering, and minimal reconnaissance. While the CVSS score is 7.1, the relative ease of exploitation and the direct business impact on service integrity push this toward immediate remediation priority. Organizations with multiple customer workspaces or internal teams using shared TypeBot instances face the highest risk.

Risk score, explained

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/I:H/A:L yields a score of 7.1 (HIGH). Attack Vector is Network (AV:N) because the application is internet-accessible. Attack Complexity is Low (AC:L)—no special conditions or race conditions are required. Privileges Required is Low (PR:L)—any authenticated user qualifies. User Interaction is None (UI:N). Scope is Unchanged (S:U) because the impact is confined to TypeBot resources. Integrity Impact is High (I:H) due to unrestricted modification or deletion of theme templates. Availability Impact is Low (A:L) because while individual templates can be destroyed, the overall service remains operational. Confidentiality remains None (C:N) as the vulnerability does not leak sensitive data beyond what might already be observable.

Frequently asked questions