EUVD-2026-67032
GHSA-h84g-8x85-mw8v
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify Baserow instance via network scan
-
DeliverySend unauthenticated HTTP request to Application Builder dispatch endpoint
-
ExploitEnumerate sequential integer data source IDs
-
ExecutionService discards permission denial and dispatches data source under integration credentials
-
ImpactAll configured rows and fields returned to attacker
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | No special conditions are required beyond the Baserow Application Builder feature being enabled and at least one data source being configured within it. The API views are declared with a permission class that admits all callers, and the service layer ignores the result of the permission check regardless of caller identity. Exploitation is bounded to Application Builder data sources specifically - standard Baserow database tables not exposed via that feature are not affected by this path. Attackers must enumerate sequential integer data source IDs, which is trivial but requires iteration over a small keyspace. No authentication is required; network reachability to the Baserow API is the only prerequisite. |
| Impact | The CVSS 4.0 score of 8.7 (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H) accurately reflects real-world risk. The attack requires no authentication, no special configuration beyond the Application Builder feature being active with data sources configured, and no user interaction, making exploitation trivially reachable from any network. Sequential integer data source IDs further reduce attack friction to a simple enumeration loop. There is no CISA KEV listing confirming active exploitation, and no public proof-of-concept has been identified at time of analysis - however, the low complexity means the gap between vulnerability disclosure and weaponization is narrow. The patch reference is a GitHub blob at tag 2.3.1 rather than a formal release advisory, so the fix version is confirmed by source diff and VulnCheck reporting but not independently verified via an official vendor changelog. Data exposure is scoped to Application Builder data sources; standard Baserow database tables not exposed through that feature are not directly reachable via this flaw. |
| Exploit ScenarioDerived | An unauthenticated attacker sends HTTP GET or POST requests to Baserow's Application Builder data source dispatch endpoint, iterating integer IDs beginning at 1. For each valid data source ID the server returns, the backend dispatches the source using the integration's stored credentials and delivers all configured rows and fields back to the attacker. No credential, session cookie, or API key is required, and a complete enumeration of all configured data sources can be scripted in minutes. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 27, 2026
Unauthenticated data disclosure in Baserow's Application Builder exposes all configured data source records to any caller due to a discarded permission check result. The dispatch and record-name API views accept requests from unauthenticated callers, and the underlying service calls check_multiple_permissions without requesting it to raise on denial - the returned denial mapping is silently ignored, allowing execution to proceed and the data source to be dispatched using the integration's own stored credentials. Because data source identifiers are sequential integers, any network-reachable attacker can enumerate all Application Builder data sources and retrieve every row and field they expose. No public exploit has been identified at time of analysis.
RemediationAI
Upgrade Baserow to version 2.3.1 or later, which resolves the flaw by passing raise_exception=True to check_multiple_permissions, causing the service to abort on any permission denial rather than silently continue. The patched source is visible at https://github.com/bram2w/baserow/blob/2.3.1/backend/src/baserow/contrib/builder/data_sources/service.py. If immediate upgrade is not feasible, restrict network access to Baserow's Application Builder dispatch API routes to authenticated internal networks or VPN - note this trade-off: publicly accessible applications relying on these data sources will break for legitimate end users. As a parallel measure, audit all configured Application Builder data sources and identify which contain sensitive records; consider disabling or removing high-sensitivity data sources until patching is complete. No version number beyond 2.3.1 is independently confirmed from a formal release note, so verify against the upstream repository after upgrading.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Baserow is an open-source no-code database platform featuring an Application Builder that lets users wire external data sources into published web applications. The vulnerability is a textbook CWE-862 (Missing Authorization) 'check-but-ignore' pattern: the dispatch and record-name views in backend/src/baserow/contrib/builder/api/data_sources/views.py are registered with a permissive permission class that does not restrict unauthenticated callers. DataSourceService.dispatch_data_sources in backend/src/baserow/contrib/builder/data_sources/service.py calls check_multiple_permissions but omits the raise_exception=True parameter, so the framework returns a mapping of denied permissions rather than raising. Since that mapping is never examined or acted upon, the service unconditionally proceeds to dispatch the requested data source under the integration's stored credentials. Affected scope covers all Baserow versions prior to 2.3.1, as identified by CPE cpe:2.3:a:baserow:baserow:*:*:*:*:*:*:*:*. The fix in 2.3.1 passes raise_exception=True to the same call, converting a silent no-op into an enforced authorization gate.
Know when Baserow gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Network-reachable unauthenticated endpoint, no complexity or interaction required, full confidentiality loss of data source contents; no integrity or availability impact.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
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.
Executive ViewAI
Baserow Application Builder contains a critical vulnerability allowing unauthenticated remote access to all data stored in configured data sources. The flaw creates immediate risk of unauthorized data exposure and potential regulatory violations for organizations using Baserow. Rapid patching across all instances is required to restore data protection controls.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
SQL injection in Baserow 2.3.3's index() formula function allows low-privileged authenticated users to supply an undocum
SSRF in URL file upload in Baserow <1.1.0 allows remote authenticated users to retrieve files from the internal server n
Baserow before 2.3.0 exposes cross-workspace data disclosure through its unique_row_values field endpoint, which lacks a
Stored cross-site scripting in Baserow's rich-text mention renderer allows any authenticated workspace member - at the l
Exploit-DB