Summary
A missing authorization check in Budibase's webhook schema-building endpoint allows unauthenticated users to modify the body schema of existing webhooks.
When an attacker can reach the /api/webhooks/schema path in affected deployments, they may mutate automation trigger output schemas, potentially impacting downstream workflows and data integrity.
Affected context
This vulnerability affects Budibase installations where:
- The builder routes are exposed and accessible over a network interface
- The generic authorization middleware is used to protect builder APIs
- The
/api/webhooks/schemaendpoint is reachable without additional network-layer controls (e.g., internal-only access, VPN)
In this context, the schema-building endpoint is registered under builder routes, but the authorization middleware intentionally or unintentionally excludes all paths matching /api/webhooks/schema from authorization checks.
Exploit preconditions
- Attack surface: HTTP(S) API endpoint at
/api/webhooks/schema - Required access: Network access to the Budibase builder API; no application-level authentication required
- Trigger point: Sending crafted requests to the webhook schema-building endpoint for an existing or discoverable webhook
- Why exploitation is possible: The generic authorization middleware explicitly skips authorization for all paths matching
/api/webhooks/schema, leaving the endpoint unprotected while still allowing updates to webhook body schemas and associated automation trigger output schemas
Why this happens
The root cause is a logical access control error consistent with CWE-862: Missing Authorization.
The webhook schema-building endpoint is placed under routes that are expected to be guarded by a generic authorization middleware, but the middleware configuration exempts all paths matching /api/webhooks/schema from authorization checks.
As a result, the endpoint processes schema update requests without verifying the caller's identity or permissions, breaking the assumption that only authenticated builders or administrators can alter automation schemas.
Potential impact
- An attacker could modify the body schema of known webhooks, changing how incoming data is interpreted.
- Automation trigger output schemas could be mutated, potentially corrupting downstream workflow data or causing unexpected automation behavior.
- Integrity of automation logic and associated data flows may be compromised, leading to misrouted actions or inappropriate processing of inputs.
- Logging, monitoring, or compliance workflows dependent on schema correctness could be disrupted or produce misleading records.
General mitigation guidance
Effective mitigation generally focuses on tightening access control around sensitive builder and configuration endpoints.
Common defensive patterns include:
- Ensuring all schema- or configuration-modifying endpoints are consistently wrapped in authorization checks that validate both authentication and appropriate roles/permissions.
- Using explicit allowlists or route-level access control definitions instead of broad pattern-based exclusions in middleware configurations.
- Restricting network exposure of builder and administrative APIs (for example, limiting them to internal networks or management VPNs) to reduce the attack surface.
- Applying least-privilege principles to accounts that can modify webhooks and automation schemas so that even authenticated misuse is constrained.
How teams detect issues like this
Organizations can detect similar authorization issues by:
- Performing regular access control reviews of route and middleware configurations, focusing on wildcard exclusions or pattern-based skips.
- Using static analysis or configuration linting rules that flag endpoints whose HTTP handlers modify configuration, schemas, or automation logic without explicit authorization checks.
- Implementing centralized logging of schema changes for webhooks and automations, including the source IP, user context (if any), and timestamps, then monitoring for unusual or unauthenticated changes.
- Incorporating automated tests or security-focused integration tests that verify sensitive endpoints return authorization errors when accessed without valid credentials.

