CVE-2026-113359: Baserow before 2.3.0 Cross-Workspace Data Disclosure via unique_row_values Endpoint
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-08 00:03 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
Baserow before 2.3.0 contains a missing authorization vulnerability that allows any authenticated user to read field values from other workspaces via the unique_row_values API endpoint. Attackers can enumerate sequential field IDs to retrieve up to 100 distinct cell values per field from tables in workspaces they do not belong to.
Description quoted from the CVE record (assigned by VulnCheck, published 2026-10-20).
Weakness: Authorization Bypass Through User-Controlled Key
How it can be exploited
Exploitable over the network with low attack complexity with no special attack requirements needing low privileges and no user interaction. Impact: confidentiality low, integrity none, availability none. CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: partial.
Public exploit evidence (Exploit Observer)
Exploit Observer found 3 code repositories naming this CVE.
Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.
See all 6 references on Exploit Observer
Live scores
- EPSS
- 0.003
low predicted chance of attack - VEDAS
- 0.988
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| Baserow | before 2.3.0 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Fixed versions stated in the CVE record: 2.3.0.
Vendor guidance:
- GitHub Security Advisory (GHSA-r8cf-4rgr-x5cv) (vendor-advisory)
- https://github.com/baserow/baserow/commit/6884c1a49adb5eb0a32de1220e6d9f99e9d97c1f (patch)
- Baserow 2.3.0 Release Notes (release-notes)
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-113359 Baserow - Broken Access Control. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-113359 Baserow - Broken Access Control"; flow:established,to_server; http.uri; content:"/api/database/fields/"; nocase; content:"/unique_row_values/"; nocase; fast_pattern; distance:0; classtype:web-application-attack; reference:cve,CVE-2026-113359; reference:url,https://www.exploit.observer/?keyword=CVE-2026-113359&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=baserow&match=exact; sid:1078602; rev:1;)
CVE-2026-113359.rules on GitHub
References
Vendor advisories and patches
- GitHub Security Advisory (GHSA-r8cf-4rgr-x5cv) (vendor-advisory)
- https://github.com/baserow/baserow/commit/6884c1a49adb5eb0a32de1220e6d9f99e9d97c1f (patch)
- Baserow 2.3.0 Release Notes (release-notes)
Technical analysis and advisories
- https://github.com/baserow/baserow/issues/4870 (issue-tracking)
- https://github.com/baserow/baserow/blob/2.2.2/backend/src/baserow/contrib/database/api/fields/views.py (technical-description)
- VulnCheck Advisory: Baserow before 2.3.0 Cross-Workspace Data Disclosure via unique_row_values Endpoint (third-party-advisory)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners
