CVE-2026-19754 Baserow CVE debrief

Who should care

Defenders responsible for Baserow installations, especially those with low-privileged users who can create or modify Formula fields, should assess exposure and prioritize remediation.

Why it matters

Defenders should prioritize verifying and remediating this vulnerability in Baserow installations, especially in environments with low-privileged users who can create or modify Formula fields, as it could lead to data exposure or modification, elevation of privileges, or disruption of database operations.

• Potential data exposure or modification outside user workspace permissions
• Elevation of privileges for low-privileged users
• Possible disruption of Baserow database operations

Technical summary

The SQL injection vulnerability in Baserow versions 2.2.0 through 2.3.3 allows a low-privileged authenticated user to provide a malicious Formula field value. This value is executed with the privileges of the Baserow PostgreSQL role, potentially allowing data to be read or modified outside the user's workspace permissions. The vulnerability is in the index() formula function, which interpolates a provided fourth argument directly into a PostgreSQL expression. This could lead to data exposure or modification, elevation of privileges, or disruption of database operations.

Defensive priority

Defenders should prioritize verifying and remediating this vulnerability in Baserow installations, especially in environments with low-privileged users who can create or modify Formula fields.

Recommended defensive actions

• Verify Baserow version and apply patches or updates to remediate the vulnerability
• Restrict access to Formula field creation and modification to privileged users only
• Monitor Baserow database activity for suspicious SQL queries
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is confirmed in Baserow versions 2.2.0 through 2.3.3, with an SQL injection vulnerability in the index() formula function. The CVE record and NVD entry provide details on the vulnerability.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.