CVE-2026-45718
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBudibase is an open-source low-code platform. Prior to 3.38.1, 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. This vulnerability is fixed in 3.38.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe row action trigger endpoint (POST /api/tables/:sourceId/actions/:actionId/trigger) in Budibase versions prior to 3.38.1 fails to validate that the user-supplied rowId is within the scope of view-level row filters. This allows authenticated users with access to a filtered view to bypass security filters and trigger row actions on any row in the underlying table, including rows explicitly excluded by the view's security configuration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Budibase installationLocate the Budibase service or application - typically runs on port 10000 or check for budibase processes/servicesAffected if Budibase is present in the environment
-
Check Budibase versionAccess the Budibase admin panel or check the container/service version metadata. Compare the installed version to 3.38.1Affected if Version is lower than 3.38.1 (e.g., 3.38.0, 3.37.x, etc.)
-
Verify row action trigger endpoint existsConfirm the endpoint POST /api/tables/:sourceId/actions/:actionId/trigger is accessible in the Budibase APIAffected if The endpoint is present and responds to requests
-
Confirm view-level row filters are configuredCheck if any views exist with row-level security filters configured in BudibaseAffected if Filtered views with security configurations exist in the system
-
Check user access to filtered viewsIdentify authenticated users who have access to views with row filters and row actions enabledAffected if Users have access to filtered views that expose row actions
The environment is affected if running Budibase version lower than 3.38.1 with filtered views that have row actions enabled, allowing authenticated users to bypass view-level row security filters.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Budibase to version 3.38.1 or later, which implements proper validation of rowId against view security filters.
Upgrade to Budibase version 3.38.1 or later
- 1. Identify the current Budibase installation version by checking the running container or application metadata
- 2. If running via Docker or docker-compose, stop the current Budibase services
- 3. Pull or update to Budibase version 3.38.1 or later
- 4. Restart the Budibase services to apply the updated version
- 5. Verify the upgrade was successful by checking the application version in the UI or via API
- 6. Test that row actions through filtered views respect view-level security filters as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45718 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45718 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data