dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-45719

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Budibase is an open-source low-code platform. Prior to 3.38.1, the V1 Views API (POST /api/views) accepts a calculation parameter from the request body that is interpolated directly into a CouchDB reduce function definition without validation. Although an internal SCHEMA_MAP object defines the valid calculation types (sum, count, stats), no actual validation is performed against this map before the value is used in string interpolation. A user with Builder permissions can inject arbitrary JavaScript code that will be executed within the CouchDB JavaScript engine when the view is queried. 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 confidence

Budibase versions prior to 3.38.1 contain an arbitrary JavaScript injection vulnerability in the V1 Views API (POST /api/views). The 'calculation' parameter from the request body is directly interpolated into a CouchDB reduce function definition without validating against the SCHEMA_MAP (which defines legitimate values: sum, count, stats). Users with Builder permissions can inject malicious JavaScript that executes within the CouchDB JavaScript engine when the view is queried.

MitigationUpgrade Budibase to version 3.38.1 or later. Until then, restrict Builder permissions to trusted users only and monitor for suspicious view definitions.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Budibase version
    Locate the running Budibase version via the UI (typically in Settings > About), API endpoint (GET /api/global/self), docker image tag, or package.json version field in the installation directory
    Affected if Version is lower than 3.38.1
  2. Confirm V1 Views API accessibility
    Verify the POST /api/views endpoint is reachable by checking if the Budibase server exposes this endpoint (e.g., curl -X POST http://<host>/api/views -H 'Content-Type: application/json' -d '{}' -v)
    Affected if Endpoint responds (even with auth error, the route exists)
  3. Identify users with Builder role
    Check Budibase user management for accounts granted Builder permission (typically via GET /api/global/users or through the admin UI Users section)
    Affected if Any untrusted or compromised user has Builder-level access
  4. Inspect custom view definitions
    Review existing view definitions by querying GET /api/views or inspecting stored view configurations in the Budibase database; look for 'calculation' values that are not one of: sum, count, or stats
    Affected if Any view contains a 'calculation' parameter value other than sum, count, or stats (indicating potential injection)

You are affected if Budibase version is below 3.38.1 AND the V1 Views API is accessible AND untrusted users have Builder permissions AND/OR suspicious custom calculation values exist in view definitions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Budibase to version 3.38.1 or later. Until then, restrict Builder permissions to trusted users only and monitor for suspicious view definitions.

Recommended fix High confidence

3.38.1 or later

  1. 1. Identify current Budibase version via admin console or CLI (usually found in settings/about)
  2. 2. Upgrade Budibase to version 3.38.1 or later by following your deployment method (Docker, Kubernetes, or native install)
  3. 3. Verify the upgrade was successful by checking the version number matches 3.38.1 or newer
  4. 4. As a precaution, restrict Builder role permissions until upgrade is complete

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45719 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45719 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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