/

CVE-2026-82870

Severity:

CRITICAL RISK

(9.6)

Authorization Bypass (CWE-639) in ToolJet Database

CVE-2026-82870

Deferred

Vulnerability type

Category:

Authorization Bypass

CWE:

CWE-639

Impact:

Cross-Tenant Database Manipulation and Destruction

Severity:

CRITICAL RISK

(9.6)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A missing organization-ownership check in ToolJet database write and destroy routes allows builder-role users to operate on databases belonging to other organizations. Under shared-instance conditions, an attacker may insert data, alter schemas, or permanently delete tables across tenant boundaries.

Affected context

The vulnerability occurs in ToolJet deployments where multiple organizations share database infrastructure and builder-role users can access database write or destroy functionality. Risk is present when these routes accept an organization identifier without reliably resolving and verifying that the requesting user is authorized to manage the referenced organization.

Exploit preconditions

  • Attack surface: ToolJet database write and destroy API routes
  • Required access: An authenticated user with builder-level privileges
  • Trigger point: A request that references a database or organization outside the user's authorized tenant
  • Why exploitation is possible: Organization ownership checks are missing or incomplete, allowing attacker-controlled identifiers to cross tenant boundaries

Why this happens

The underlying bug is an authorization failure caused by trusting an organization identifier without enforcing ownership at the point where database operations are performed. This maps to CWE-639: Authorization Bypass Through User-Controlled Key, where a user-controlled key selects a protected resource and the application fails to verify that the requester is permitted to access it. As a result, route-level permissions may be satisfied while tenant-level authorization is bypassed.

Potential impact

  • Attackers may insert arbitrary data into another organization's database
  • Attackers could alter database schemas or disrupt application behavior
  • Attackers may permanently delete tables and associated data
  • Cross-tenant confidentiality, integrity, and availability could be affected
  • Shared-instance customers could experience data loss or service disruption

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every database operation and deriving tenant context from trusted server-side identity rather than request parameters.

Common defensive patterns include:

  • Resolve organization and database ownership server-side from the authenticated session
  • Enforce tenant authorization checks immediately before read, write, schema, and destroy operations
  • Treat organization identifiers supplied by clients as untrusted selectors
  • Apply deny-by-default policies for cross-organization resource access
  • Separate database credentials and permissions by tenant where practical
  • Require additional safeguards for destructive schema and data operations
  • Use least-privilege roles and independent audit logging for administrative actions

How teams detect issues like this

Organizations can detect similar authorization flaws through:

  • Static analysis for routes that use client-supplied organization or resource identifiers without ownership checks
  • Code review of every database mutation and destructive operation for server-side tenant resolution
  • Policy tests that attempt cross-organization access with valid lower-privilege accounts
  • API monitoring for unusual cross-tenant identifiers, bulk mutations, schema changes, and table deletions
  • Audit-log correlation between actor identity, organization context, and affected database resource
  • Automated security testing and neutral code-review tools that flag missing object-level authorization

Sources

SourceLink
github.comgithub.com/ToolJet/ToolJet/security/advisories/GHSA-xr3w-r926-xfmm
vulncheck.comvulncheck.com/advisories/tooljet-before-3.16.208-cross-tenant-database-manipulation

Frequently asked

questions

Yes, where the affected ToolJet routes are reachable through the application and an attacker has a valid builder-role account. Exploitation does not require administrative privileges if tenant authorization remains unenforced.

The attacker generally needs authenticated builder-level access to the shared ToolJet instance and the ability to invoke database write or destroy functionality.

Resolve the organization context from trusted server-side authorization data and enforce ownership checks on every database operation, especially schema changes and destructive actions.

Use centralized object-level authorization, deny-by-default tenant policies, cross-tenant negative tests, least-privilege database permissions, and comprehensive audit logging.

Find out what's already
exploitable in your codebase.