Summary
Budibase Server before 3.41.3 contains a server-side request forgery vulnerability in its query import endpoint because user-supplied URLs are not adequately validated before being fetched. An attacker who can reach the endpoint may use the server to retrieve responses from internal services, cloud metadata endpoints, or other restricted network resources.
Affected context
The vulnerability occurs in Budibase Server deployments where the query import endpoint accepts a user-controlled URL and causes the server to retrieve content from that location. Risk is higher when the server can access internal administration interfaces, cloud instance metadata services, private APIs, or other network segments that are not directly reachable by an external requester.
Exploit preconditions
- Attack surface: The Budibase query import endpoint
- Required access: Ability to submit requests to the endpoint, subject to the deployment's authentication and authorization controls
- Trigger point: Server-side fetching of a user-supplied URL
- Why exploitation is possible: URL validation does not sufficiently restrict destinations, allowing the server to act as a proxy toward internal or otherwise restricted resources
Why this happens
The underlying bug is insufficient validation and authorization of a user-controlled network destination before the application performs a server-side request. This maps to CWE-918: Server-Side Request Forgery (SSRF), where an application makes outbound requests on behalf of an attacker without enforcing an appropriate destination policy. The insecure pattern occurs when externally influenced URLs are passed to a network client without robust controls for allowed schemes, hosts, address ranges, redirects, and resolution behavior.
Potential impact
- An attacker may retrieve sensitive responses from internal services
- Cloud instance credentials or metadata may be exposed
- Internal administrative interfaces could be probed or accessed
- The vulnerability could support follow-on compromise of connected services
- Network topology and service information may be disclosed
General mitigation guidance
Mitigation generally focuses on reducing trust in user-supplied destinations and enforcing a restrictive outbound request policy.
Common defensive patterns include:
- Allowing requests only to explicitly approved hosts, schemes, and ports
- Blocking loopback, link-local, private, multicast, and reserved address ranges
- Resolving and validating destinations before connection, while accounting for DNS rebinding
- Restricting or disabling redirects unless each destination is revalidated
- Routing outbound requests through controlled egress proxies or network policies
- Applying least-privilege identity permissions so metadata or internal services expose minimal value
- Separating application workloads from sensitive management and metadata networks where practical
How teams detect issues like this
Organizations can identify SSRF risks through:
- Static analysis for network clients that consume request parameters or other untrusted URL sources
- Code review checks for missing scheme, hostname, port, redirect, and IP-range validation
- Tests covering loopback, private, link-local, encoded, redirected, and DNS-rebinding destinations
- Egress firewall and proxy policies that alert on requests to internal or metadata address ranges
- Application logs correlating user-controlled URLs with outbound requests and unusual response targets
- Automated security review tools that flag externally influenced server-side network requests

