Summary
A server-side request forgery vulnerability in Budibase allows builder-level users to submit arbitrary URLs through the datasource verification endpoint without adequate SSRF validation. An attacker may use this behavior to reach internal services, expose CouchDB credentials, and potentially obtain broad database access in cloud deployments.
Affected context
The issue affects Budibase Server deployments where the datasource verification endpoint is accessible to builder-level users and accepts user-supplied URLs without sufficiently restricting destination addresses. Risk is greater in cloud environments when internal services, metadata endpoints, or CouchDB instances are reachable from the application network.
Exploit preconditions
- Attack surface: The datasource verification endpoint
- Required access: A builder-level Budibase account or equivalent permission to invoke datasource verification
- Trigger point: Submission of an attacker-selected URL for datasource validation
- Why exploitation is possible: The server makes outbound requests without adequately validating or restricting the requested destination, allowing access to internal network services
Why this happens
The vulnerability results from treating a user-controlled URL as an acceptable server-side request target without enforcing a strong destination policy. This maps to CWE-918: Server-Side Request Forgery, where application-controlled network requests can be redirected to internal, restricted, or otherwise unintended services.
Potential impact
- Internal services may be accessed from the Budibase server's network position
- CouchDB credentials or other sensitive responses could be disclosed
- Attackers could gain unauthorized database access
- Cloud metadata or internal administrative interfaces may be exposed
- Data confidentiality and integrity could be compromised
General mitigation guidance
Mitigation generally focuses on reducing trust in user-supplied URLs and enforcing secure outbound request policies.
Common defensive patterns include:
- Allowing requests only to explicitly approved schemes, hosts, ports, and destinations
- Blocking loopback, link-local, private, and reserved address ranges after DNS resolution
- Revalidating destinations across redirects and protecting against DNS rebinding
- Separating datasource verification from privileged internal network access
- Using dedicated egress controls, network segmentation, and least-privilege service credentials
- Avoiding exposure of database credentials in responses and limiting their scope where possible
How teams detect issues like this
Detection approaches commonly include:
- Static analysis for outbound HTTP clients receiving URLs from request parameters
- Code review checks for missing allowlists, private-address filtering, redirect validation, or DNS rebinding defenses
- Runtime monitoring of datasource verification requests to internal, loopback, link-local, and cloud metadata addresses
- Egress firewall and service-mesh policies that restrict application-originated destinations
- Alerting on unusual outbound requests, unexpected response contents, or repeated verification attempts
Automated security review tools may help identify URL-fetching paths that lack destination validation.

