Budibase: SSRF via OAuth2 Config Validation — Missing fetchWithBlacklist Protection
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Budibase | budibase | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Budibase | Budibase |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-g6qx-g4pr-92v7 | Budibase: SSRF via OAuth2 Config Validation — Missing fetchWithBlacklist Protection |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.217% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Budibase
Budibase budibase |
|
| Vendors & Products |
Budibase
Budibase budibase |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Budibase is an open-source low-code platform. Prior to 3.39.0, the OAuth2 token fetch function in packages/server/src/sdk/workspace/oauth2/utils.ts uses raw fetch(config.url) with no SSRF protection. The safe wrapper fetchWithBlacklist() exists in the same codebase and is used in every other outbound HTTP call (automation steps, plugin downloads, object store), but was not applied to the OAuth2 token endpoint. A user with BUILDER role can point the OAuth2 token URL to internal services (CouchDB, cloud metadata) to exfiltrate sensitive data. This vulnerability is fixed in 3.39.0. | |
| Title | Budibase: SSRF via OAuth2 Config Validation — Missing fetchWithBlacklist Protection | |
| Weaknesses | CWE-918 | |
| References |
| |
| Metrics |
cvssV3_1
|