Baserow dispatches an Application Builder data source without acting on the result of its permission check. The dispatch and record-name views in backend/src/baserow/contrib/builder/api/data_sources/views.py are declared with a permission class that admits any caller, so a request carrying no credential reaches the handler. DataSourceService.dispatch_data_sources in backend/src/baserow/contrib/builder/data_sources/service.py then calls check_multiple_permissions without asking it to raise, and neither stores nor examines the mapping of denials it returns, so a denied check leaves execution to continue and the data source is dispatched whatever the caller's identity. The dispatch runs with the integration's own credentials, so an unauthenticated request naming a data source receives the rows and fields that source reads. Identifiers are small integers and can be enumerated. Version 2.3.1 passes raise_exception to the same call.

CVE-2026-81335 affects Baserow versions prior to 2.3.1, exposing a critical authorization bypass in the Application Builder's data source dispatch mechanism. The dispatch and record-name API views are configured with a permissive class that allows any caller, including unauthenticated requests, to reach the handler. The DataSourceService.dispatch_data_sources method calls check_multiple_permissions but never evaluates or stores the denial mapping it returns, allowing execution to continue regardless of permission outcome. As a result, the data source is dispatched using the integration's own credentials, leaking rows and fields to unauthenticated callers. Data source identifiers are small integers, making them trivially enumerable and increasing the risk of mass data exposure. The fix in version 2.3.1 passes the raise_exception flag to the permission check, ensuring denials halt execution. This vulnerability enables unauthenticated data exfiltration from any Baserow Application Builder data source. Organizations using Baserow should upgrade to version 2.3.1 immediately.