CVE-2026-45717
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, Budibase exposes a REST API for datasource management. The route PUT /api/datasources/:datasourceId is registered in the authorizedRoutes group with TABLE/READ permission. This is the same authorization level as the read endpoint (GET /api/datasources/:datasourceId). Every authenticated Budibase app user with the BASIC built-in role or higher carries TABLE/WRITE (and therefore TABLE/READ) permissions, and the datasource update controller performs no additional builder check. As a result, any authenticated non-builder app user can submit a PUT request to rewrite a datasource's config object — including the connection host, port, database credentials, or the base url of a REST datasource. Because no network-level SSRF protection is applied to SQL driver connections, redirecting a PostgreSQL/MySQL/MongoDB datasource to an internal IP address succeeds and the attacker can probe or interact with internal services on arbitrary ports. 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 confidenceIn Budibase prior to 3.38.1, the PUT /api/datasources/:datasourceId endpoint was incorrectly registered with TABLE/READ permission, allowing any authenticated user with BASIC role or higher to modify datasource configurations (connection strings, credentials, REST base URLs). No builder check or SSRF protection was enforced, enabling attackers to redirect SQL database connections to internal IP addresses and probe internal services.
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
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 versionCheck the Budibase installation for its version number. This is typically visible in the admin UI (often on an 'About' or 'Settings' page), in the docker container metadata, or in a package.json file if self-hosted. Compare this version to 3.38.1.Affected if The installed version is before 3.38.1 (e.g., 3.38.0, 3.37.x, etc.)
-
Verify API endpoint authorizationUsing an authenticated session with a BASIC role user, send a PUT request to /api/datasources/:datasourceId with a modified configuration payload (e.g., change connectionString or REST base URL). Observe whether the request succeeds or is rejected.Affected if The PUT request succeeds and modifies the datasource configuration without returning a 403 Forbidden or authorization error, indicating the endpoint accepts BASIC role access
-
Review datasource modification permissionsIn the Budibase admin panel, navigate to the permissions or access control settings. Check which roles are permitted to modify datasource configurations under the datasource API endpoints.Affected if Users with BASIC role are granted permission to modify datasource configurations, or the datasource PUT endpoint is mapped to TABLE/READ permission
You are affected if your Budibase installation is version 3.38.0 or earlier and the PUT /api/datasources/:datasourceId endpoint accepts requests from users with BASIC role or higher.
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 authorization validation and SSRF protection for datasource connections.
3.38.1
- Identify the current Budibase version by checking the installed instance or configuration
- Review the Budibase release notes for version 3.38.1 to understand changes and ensure compatibility
- Create a backup of the current Budibase instance including databases, configurations, and any custom datasources
- Upgrade Budibase to version 3.38.1 following the official upgrade documentation for your deployment method (Docker, Kubernetes, or direct installation)
- After upgrade, verify that the PUT /api/datasources/:datasourceId endpoint now requires proper TABLE/WRITE authorization
- Test that legitimate users with BASIC roles can no longer modify datasource configurations without appropriate permissions
- Confirm the vulnerability is remediated by attempting (in a test environment) a PUT request to the datasource endpoint as a non-builder user
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45717 — 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-45717 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