CVE 8.8 HIGH

Budibase: `PUT /api/datasources/:datasourceId` is protected only by `TABLE/READ` permission instead of builder access, allowing any authenticated app user to overwrite datasource connection parameters including host, port, and URL._CVE-2026-45717

8.8 / 10
HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Description

Budibase 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.

AI Analysis

Any authenticated non-builder app user can submit a PUT request to rewrite a datasource's config object, including connection host, port, database credentials, or base URL of a REST datasource, due to insufficient authorization and lack of SSRF protection.

Basic Information

ID CVE-2026-45717
Source GitHub_M
Published May 27, 2026 at 17:09
Modified May 27, 2026 at 17:57

Affected Product

Vendor Budibase
Product budibase
Version < 3.38.1
Affected Versions Budibase budibase < 3.38.1

CWE Classification

AI Assessment

AI Score 8.8 / 10
AI Severity High
Vendor Budibase
Product Budibase
Version < 3.38.1

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.