# CVE-2026-19754: Baserow 2.2.0 through 2.3.3 - SQL injection in formula index() JSONB array extraction

> Low-privileged users can inject SQL via formula fields to read or modify data outside their workspace permissions.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-389p-g792-49fp

## What is CVE-2026-19754?

CVE-2026-19754 is a high-severity SQL injection vulnerability in Baserow, published on 2 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Baserow versions 2.2.0 through 2.3.3 contain an SQL injection vulnerability in the index() formula function. A low-privileged authenticated user who can create or modify Formula fields can provide an undocumented fourth argument that is treated as a SQL template and interpolated directly into a PostgreSQL expression. The generated SQL executes through Baserow's database connection with the Baserow PostgreSQL role permissions, allowing data outside the user's workspace permissions to be read or modified.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-19754?


## How do I fix CVE-2026-19754?

No fix has been published for CVE-2026-19754 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-19754 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19754 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19754 and fix it if it is affected.

What it is: CVE-2026-19754 is a high-severity SQL injection vulnerability in Baserow, published on 2 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19754 exists.

Affected product: Baserow. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19754/ (Markdown: https://insights.sbomify.com/CVE-2026-19754/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19754
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19754
- OSV: https://osv.dev/vulnerability/CVE-2026-19754

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19754/
Summaries are generated and may contain mistakes; the official description above is the record.