dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-48151

HIGH · 7.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 →
84/100
Remediation priority · High
Remotely reachable No privileges 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.39.0, the webhook schema-building endpoint is registered under builderRoutes, but the generic authorization middleware skips authorization for all paths matching /api/webhooks/schema. As a result, an unauthenticated caller can update the body schema for a known webhook and mutate the corresponding automation trigger output schema. This vulnerability is fixed in 3.39.0.

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.39.0 contain an authorization bypass vulnerability where the generic authorization middleware incorrectly skips authentication for all endpoints matching /api/webhooks/schema. This allows unauthenticated attackers to update the body schema for known webhooks and manipulate the corresponding automation trigger output schema, potentially altering application behavior.

MitigationUpgrade to Budibase version 3.39.0 or later. Additionally, audit the authorization middleware to ensure all builderRoutes endpoints enforce proper authentication regardless of path patterns.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 installation and version
    Check the Budibase version running in your environment. This is typically found in the UI footer, in package.json files if self-hosted, or via API endpoint /api/self. Compare against the affected range: versions prior to 3.39.0.
    Affected if The installed Budibase version is below 3.39.0.
  2. Verify /api/webhooks/schema endpoint accessibility
    Send an unauthenticated HTTP request to your Budibase instance at the endpoint /api/webhooks/schema. For example: curl -X GET https://your-budibase-host/api/webhooks/schema (no auth headers).
    Affected if The endpoint returns a valid HTTP response (200 or similar) without requiring authentication.
  3. Check for existing webhook configurations
    If the endpoint is accessible, enumerate existing webhooks by querying /api/webhooks or through the Budibase UI to identify which webhooks could be targeted for schema manipulation.
    Affected if Any webhooks exist in the Budibase instance and the /api/webhooks/schema endpoint is unauthenticated.

You are affected if Budibase version is below 3.39.0 AND the /api/webhooks/schema endpoint is reachable without authentication, allowing unauthorized schema modifications on configured webhooks.

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 to Budibase version 3.39.0 or later. Additionally, audit the authorization middleware to ensure all builderRoutes endpoints enforce proper authentication regardless of path patterns.

Recommended fix Moderate confidence

3.39.0

  1. 1. Identify the currently running Budibase version by checking the deployment or configuration
  2. 2. For Docker-based deployments: stop the existing container and pull the new image tagged 3.39.0 or later (e.g., docker pull budibase/budibase:3.39.0)
  3. 3. For Kubernetes-based deployments: update the deployment manifest to use image version 3.39.0 or later and apply the changes (kubectl set image deployment/budibase budibase=budibase/budibase:3.39.0)
  4. 4. For self-hosted installations using a package manager: run the appropriate upgrade command for your package manager to update to version 3.39.0
  5. 5. After upgrading, verify the /api/webhooks/schema endpoint now requires proper authorization
  6. 6. Test that existing webhooks and automations continue to function correctly after the upgrade
Caveat Review Budibase 3.39.0 release notes for any migration steps or configuration changes that may affect existing setups

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48151 — 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-48151 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