AI Science Tracker
EN

Baserow: SQL injection in formula processing

Baserow · AI involvement attributed to Fluid Attacks AI SAST Scanner (specific model not disclosed)

Finding and attribution

Baserow 2.2.0 through 2.3.3 has an SQL-injection issue in formula processing. The individual source reports possible database disclosure and changes to application authorization data, requiring authenticated formula-editing access. The individual advisory attributes detection to Fluid Attacks' AI SAST Scanner and disclosure to Miguel Gómez.

What to update · Baserow

Affected versions not confirmed in this summary.

Remediation note: The individual advisory documents an upstream correction in 2.3.4 or later and a patch date after the public disclosure. A fixed release statement does not establish installed updates.

Advisory / fix evidence · checked 21 Nov 2026

Product: Baserow. AI system: Fluid Attacks AI SAST Scanner (specific model not disclosed). Team / organization: Fluid Attacks.

CVE identifiers: CVE-2026-19754.

AI and human contribution (source account): The individual first-party advisory explicitly distinguishes detection by AI SAST Scanner from disclosure by Miguel Gómez of Fluid Attacks' Offensive Team. Detailed model architecture and the division of discovery and human validation tasks are not disclosed.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: Public individual advisory and matching primary CNA record. Unknown zero-day status is not inferred. The checked page provides an advisory release date but does not independently establish when its present AI-attribution wording was first public.

Remediation status: fix documented.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 2 Sep 2026. AI attribution date not established by the source. Sources checked 21 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Not available · no assessment established here. Documented technical effects: Not available.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

No source-backed CVSS assessment is established in this catalog.

Technical effects, prerequisites and exploitation evidence are not established here. Missing evidence does not establish absence of exploitation.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases