TypeBot versions before 3.16.0 contain an incorrect authorization vulnerability (CWE-863) in the getLinkedTypebots API endpoint. The endpoint returns full bot definitions to any authenticated user referencing a target bot ID, regardless of workspace ownership. The root cause is misuse of an async callback with Array.filter(), which is synchronous, resulting in the access control predicate always evaluating as true. This allows unauthorized access to private bot data including conversation blocks, logic flow, sensitive variables, and integration details. The vulnerability is addressed in version 3.16.0.

Any authenticated user of TypeBot prior to version 3.16.0 can access private bot definitions belonging to other workspaces. This exposure includes sensitive information such as credentials, API keys, personally identifiable information, webhook URLs, and integration configurations. The confidentiality of private workspace data is compromised, but there is no indication of impact to integrity or availability. No known exploits in the wild have been reported.

Upgrade TypeBot to version 3.16.0 or later, where this authorization issue has been fixed. Since this is a self-hosted product, users must apply the update themselves. Patch status is confirmed by the vendor advisory stating the fix is included in version 3.16.0. Until upgraded, restrict authenticated user access where possible to limit exposure.