Summary
A command injection vulnerability in Budibase allows unauthenticated attackers to trigger automations that execute arbitrary Bash commands on the server via a public webhook endpoint.
When an exposed automation includes a Bash step, an attacker can invoke it without credentials, leading to remote code execution running as root inside the container.
Affected context
This vulnerability affects Budibase deployments that expose public webhook endpoints tied to automations containing a Bash step or shell execution capability.
Risk is highest when:
- Public webhooks are reachable from the internet or untrusted networks
- Automations are configured to run arbitrary shell commands
- The application container runs these steps with elevated privileges (e.g., root)
Even internal-only deployments may be impacted if untrusted users or systems can reach the webhook URL.
Exploit preconditions
- Attack surface: Public webhook endpoint used to trigger Budibase automations.
- Required access: None; no authentication or valid user account is needed.
- Trigger point: HTTP request to a webhook URL that is bound to an automation containing a Bash/shell step.
- Why exploitation is possible: The automation execution pipeline allows shell commands to be run in response to webhook calls without enforcing authentication, authorization, or strong isolation between user input and command execution.
Why this happens
The underlying issue is a design-level command injection risk (CWE-78) in the automation engine.
Budibase allows automations to include Bash steps that execute commands on the server in direct response to webhook triggers.
Because the webhook endpoint is exposed without authentication, untrusted callers can trigger workflows that run shell commands with high privileges.
The lack of an authorization boundary between the public webhook and command execution, combined with running the process as root, turns a convenience feature into a powerful execution primitive.
Potential impact
- Remote code execution on the Budibase server container as root
- Full compromise of the application runtime and its data at rest within the container
- Lateral movement to other services reachable from the compromised container
- Deployment of malware, cryptominers, or backdoors within the container environment
- Exfiltration or tampering with configuration files, secrets mounted into the container, or application logs
General mitigation guidance
Effective mitigation focuses on hardening automation design, tightening trust boundaries around webhooks, and minimizing shell execution:
- Prefer built-in, parameterized actions or SDK-based integrations instead of raw Bash or shell steps for automations.
- Treat all webhook-triggered input as untrusted; introduce authentication, signed requests, or IP allowlisting at the gateway or reverse proxy layer where feasible.
- Apply the principle of least privilege to automation execution: avoid running application containers and automation workers as root; use dedicated, minimally privileged service accounts.
- Isolate automation execution from the main application process using sandboxing, separate worker containers, or restricted execution environments to limit blast radius.
- Establish configuration guidelines that discourage or constrain arbitrary command execution in low-code automations, especially for flows exposed through public endpoints.
How teams detect issues like this
Detection generally involves reviewing automation configuration, gateway logs, and code-level patterns:
- Use configuration audits or security reviews to identify automations that:
- Include Bash/shell steps
- Are wired to public or unauthenticated webhooks
- Monitor HTTP access logs at load balancers or API gateways for:
- Unusual or high-volume calls to webhook endpoints
- Access from unexpected geographic regions or IP ranges
- Apply static or configuration analysis to the automation definitions (YAML/JSON/config) looking for command execution constructs or shell invocation patterns.
- Implement policy-as-code controls (e.g., via CI/CD checks) that flag or block deployments when automations with shell steps are exposed through unauthenticated endpoints.
- Use runtime security tooling or container monitoring to detect anomalous command execution, process spawning, or network activity from Budibase containers.

