Description

ToolJet before v3.16.208 fails to validate organization membership in database read routes, allowing any authenticated user to access other organizations' table schemas and row data. Attackers can supply arbitrary organization IDs in URL parameters to list tables, retrieve column definitions, and execute join queries to read actual stored data from victim organizations.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "7.7",
  "pubDate": "2026-08-31T09:17:08.017Z",
  "pubdate": "2026-08-31T09:17:08.017Z",
  "executiveSummary": "This vulnerability is a critical Broken Access Control (BAC) flaw affecting ToolJet versions prior to 3.16.208. The issue stems from insufficient authorization checks within the application's database read routes, which fail to validate whether an authenticated user belongs to the target organization specified in the request parameters.\nThe vulnerability allows any authenticated user to bypass organizational boundaries, granting them unauthorized access to sensitive data belonging to other organizations within the same instance. By manipulating URL parameters, an attacker can enumerate database table schemas, retrieve column definitions, and execute arbitrary join queries against victim data.\nThe impact is significant, leading to a complete compromise of confidentiality for database rows across the multi-tenant environment. Exploitation requires only a valid user account on the affected ToolJet instance and does not necessitate elevated administrative privileges. Given the nature of the flaw, attackers can extract full datasets, posing severe data privacy and security risks to all organizations hosted on the vulnerable infrastructure.",
  "technicalDetails": "The root cause of this vulnerability lies in the improper implementation of server-side access control checks within ToolJet's database interaction modules. Specifically, the application's API endpoints responsible for reading database table metadata and querying row data fail to enforce strict session-to-organization binding.\nWhen a request is made to retrieve database information, the application relies on an organization ID supplied via the URL parameter. The vulnerable components process this ID without verifying if the requesting user's session token is associated with the provided organizational scope. This trust-based mechanism assumes that the caller is authorized for the supplied ID, effectively bypassing the intended multi-tenancy isolation.\nThe exploitation process follows a logical flow: First, an authenticated attacker intercepts a valid API request to the database read route. Second, the attacker modifies the organization_id parameter in the URL to match the target organization's unique identifier. Because the backend service lacks a comprehensive authorization middleware or a verification function to check the intersection of the user's permissions and the target organization's database resources, the server processes the request as if the attacker were a legitimate member of the target organization.\nSuccessful exploitation enables an attacker to perform unauthorized reconnaissance, such as listing all available tables within the target database, inspecting column structures to map sensitive fields, and constructing complex SQL queries—including JOIN operations—to extract raw row data. This behavior persists across the entire scope of the database user configured for the connection string, potentially exposing proprietary business intelligence, PII, or credentials stored within the application.\nThis vulnerability is inherent to the application architecture in versions prior to 3.16.208 and is accessible via standard network protocols over HTTP/HTTPS. No specialized tools are required beyond a basic intercepting proxy or command-line HTTP client. The flaw effectively transforms every authenticated user into a potential threat actor capable of cross-tenant data exfiltration."
}