BaselineWatch
Desk
Your fleet and your work Fleetyour releases and the hardware they run onTriagewhat needs a decisionWatchlistthe products and platforms you runSaved searchesthe lists you come back to
This instance Sourceswhat is read, how often, under what termsDigestthe daily or weekly summary, and alerts
How it is drawn Appearancethe look and the colour schemeBrandingthe mark this instance wears
Owner sign-in

CVE-2026-19754

8.6 high SSVC exploitation: poc Published
NVD · CVE.org

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.

Fix

Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.

Change history 15

  1. StatusAwaiting Analysis → PublishedNVD modified 2026-10-23 18:30
  2. References+1 -1 references (now 5)NVD modified 2026-10-23 19:17
  3. StatusPublished → Awaiting AnalysisNVD modified 2026-10-23 19:17
  4. StatusAwaiting Analysis → PublishedNVD modified 2026-10-23 17:25
  5. References+1 -1 references (now 5)NVD modified 2026-10-23 18:17
  6. StatusPublished → Awaiting AnalysisNVD modified 2026-10-23 18:17
  7. 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 vulnerable expression is executed when Baserow recalculates Formula-field values. Because the generated SQL runs through Baserow's database connection, the injected SQL executes with the privileges of the Baserow PostgreSQL role rather than the permissions of the authenticated application user, allowing data to be read or modified outside the user's workspace permissions.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.
    NVD modified 2026-10-23 18:17
  8. StatusAwaiting Analysis → PublishedNVD modified 2026-10-20 23:40
  9. StatusPublished → Awaiting AnalysisNVD modified 2026-10-21 00:17
  10. StatusAwaiting Analysis → PublishedNVD modified 2026-10-19 23:53
  11. References-1 references (now 5)NVD modified 2026-10-20 00:17
  12. StatusPublished → Awaiting AnalysisNVD modified 2026-10-20 00:17
  13. Description
    Baserow versions 2.2.0 through 2.3.3 contain an SQL injection vulnerability in the index() formula function. An authenticated user who can create or edit Formula fields can pass an undocumented fourth argument. Baserow inserts this argument into a PostgreSQL expression. The injected SQL runs with the Baserow database role permissions and can read or modify database data outside the user's workspace permissions.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 vulnerable expression is executed when Baserow recalculates Formula-field values. Because the generated SQL runs through Baserow's database connection, the injected SQL executes with the privileges of the Baserow PostgreSQL role rather than the permissions of the authenticated application user, allowing data to be read or modified outside the user's workspace permissions.
    NVD modified 2026-10-20 00:17
  14. StatusAwaiting Analysis → PublishedNVD modified 2026-10-19 22:39
  15. First seenCVSS 8.6NVD modified 2026-10-19 23:17

Affected (CPE criteria) 0

NVD has not attached CPE configurations yet.

References 5