Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-48759

HIGH · 7.1 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

TypeBot versions 3.15.2 and below contain an Insecure Direct Object Reference (IDOR) vulnerability in the handleSaveThemeTemplate and handleDeleteThemeTemplate handlers. While the handlers correctly validate that the authenticated user is a non-guest member of a workspace, the Prisma queries operating on themeTemplateId do NOT include workspaceId in the WHERE clause, allowing any authenticated user to modify or delete theme templates from any other workspace.

MitigationUpgrade to TypeBot version 3.16.0 or later, which includes the fix for this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed TypeBot version
    Locate the TypeBot installation and determine its version number from package.json, docker image tag, or application metadata. Compare against affected range: versions 3.15.2 and below.
    Affected if Running version 3.15.2 or lower
  2. Confirm theme template feature is active
    Check if the handleSaveThemeTemplate and handleDeleteThemeTemplate API endpoints are exposed and functional in the application. This may require examining the API routes or checking if theme templates exist in the database.
    Affected if Theme template handlers are accessible and theme templates exist in the system
  3. Verify user authentication is enabled
    Confirm that the application requires authentication for workspace access. The vulnerability requires an authenticated non-guest user session to exploit.
    Affected if Authentication is enabled and users can access the workspace
  4. Audit Prisma queries for missing workspaceId filter
    Review the source code for handleSaveThemeTemplate and handleDeleteThemeTemplate handlers. Examine the Prisma queries operating on themeTemplateId and verify whether workspaceId is included in the WHERE clause.
    Affected if Queries on themeTemplateId do NOT include workspaceId in the WHERE clause

User is affected if running TypeBot version 3.15.2 or below with authenticated user access to theme template handlers, and the Prisma queries lack workspaceId validation in the WHERE clause.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to TypeBot version 3.16.0 or later, which includes the fix for this vulnerability.

Recommended fix High confidence

3.16.0

  1. Upgrade TypeBot to version 3.16.0 or later

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48759 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48759 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data