All vulnerabilities

Servers and applications

CVE-2026-45718

Row Action Trigger Bypasses View Row Filter Security Boundary Allowing Action on Out-of-Scope Rows

Severity
Medium 5.4
Published
12 May 2026
Last changed
13 May 2026
Added to UpHeron
3 Nov 2026
Fixed in
3.38.1
Exploit chance
0.1% in the next 30 daysHigher than 3% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Incorrect authorization (CWE-863)
Attack
Over the network · Needs a user account · No user action needed
Attacker can
Read some data · Change some data
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Also known as
GHSA-3263-v5v9-xq8q
Sources
Project advisories (GitHub)

Description

The row action trigger endpoint (POST /api/tables/:sourceId/actions/:actionId/trigger) fails to validate that the user-supplied rowId is within the scope of the view's row filters. A user with access to a filtered view can trigger row actions on any row in the underlying table, including rows explicitly excluded by the view's security filters.

View filters in Budibase are treated as a security boundary. The search path (packages/server/src/sdk/workspace/rows/search.ts:93-94) explicitly enforces view query filters with the comment: "that could let users find rows they should not be allowed to access."

However, the row action trigger path bypasses this enforcement entirely:

  • Route (packages/server/src/api/routes/rowAction.ts:55-59): Accepts a sourceId that can be a viewId.
  • Middleware (packages/server/src/middleware/triggerRowActionAuthorised.ts:24-55): Correctly validates that the user has READ permission on the view and that the row action is enabled for that view.
From Budibase/budibase's security advisory. Shortened; the full text is there.

Affected software

SoftwareAffected versions
BudibaseServers and applications · github:budibase/budibase
  • Every version before 3.38.1

About Budibase

low-code development platform

From Wikidata, CC0 1.0.
Docker Hub pulls
2,327,272Docker Hub, 15 Nov 2026
GitHub stars
28,419GitHub, 15 Nov 2026
Forks
2,238GitHub, 15 Nov 2026
Latest release
v4.0.0GitHub, 15 Nov 2026
Released
10 Nov 2026GitHub
First published on GitHub
7 Jun 2019GitHub

References