CVE-2026-48152
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.39.0, the single-datasource GET and PUT routes are guarded by generic TABLE READ, not by Builder/Admin permission or datasource-specific ownership/resource checks. The built-in Basic app user role maps to the WRITE permission set, which includes table read/write and query write. A Basic user can therefore read an existing REST datasource, receive redacted authConfigs values, submit an update that changes only config.url while keeping the redacted placeholders, and trigger an existing saved relative-path REST query. During update, mergeConfigs() restores the old stored secret when it sees the redaction placeholder. During query execution, Budibase prefixes the attacker-controlled datasource config.url to the relative query path and applies the resolved stored auth headers. The result is server-side disclosure of the builder-configured REST Authorization secret to an attacker-controlled listener. 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 confidenceIn Budibase before 3.39.0, the single-datasource GET and PUT routes lack proper Builder/Admin permission checks, relying only on generic TABLE READ permission. A Basic user with WRITE permissions can update a REST datasource's config.url to an attacker-controlled endpoint while preserving redacted auth placeholders. The mergeConfigs() function restores the actual stored secrets during update, and during query execution, Budibase prefixes the attacker-controlled URL to relative query paths while applying the resolved auth headers, enabling exfiltration of builder-configured REST Authorization secrets to a remote listener.
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
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check Budibase versionLocate the installed Budibase version (typically via UI at Settings > Version, or via docker ps/package.json, or by querying the API endpoint /api/global/self), then compare it to the affected range: versions before 3.39.0 are vulnerableAffected if The installed version is before 3.39.0
-
Identify REST datasourcesNavigate to the Datasources section in the Budibase UI, or query the internal API (GET /api/datasources) to list all configured datasources, noting which ones are of type RESTAffected if Any REST datasource is configured in the environment
-
Review datasource permissionsInspect the permission settings for the affected datasources: check if Basic users or non-Builder/Admin users have WRITE access to the REST datasources identified in step 2. This is typically found in the datasource settings or the Access Control sectionAffected if Basic or non-Builder/Admin users have WRITE permission on any REST datasource
-
Audit REST datasource URLsExamine the stored URL configuration for each REST datasource: query GET /api/datasources/{id} for each REST datasource and inspect the config.url field. Look for URLs pointing to unexpected or external domains that differ from the intended API endpointAffected if Any REST datasource has a config.url value set to an external or unexpected domain (especially IP addresses or domains you do not control)
A user is affected if running Budibase version below 3.39.0 AND has REST datasources accessible to Basic users with WRITE permissions, where the datasource URL may have been modified to an attacker-controlled endpoint.
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 to Budibase version 3.39.0 or later, which implements proper Builder/Admin permission checks on datasource routes.
3.39.0
- 1. Back up your current Budibase installation and database
- 2. Check your current Budibase version using the admin console or CLI
- 3. If running a self-hosted instance, update using your deployment method (e.g., Docker pull, Kubernetes helm upgrade, or yarn/npm update)
- 4. For Docker: pull the new image tag for version 3.39.0 and recreate containers
- 5. Verify the upgrade was successful by checking the version in the admin console
- 6. Test that datasource functionality works correctly after the upgrade
- 7. Confirm the vulnerability is remediated by verifying Basic users can no longer access REST datasource authorization secrets
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-48152 — 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-48152 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