Summary
Budibase contains a missing authorization vulnerability in the resource duplication endpoint. An authenticated builder may be able to inject tables, automations, queries, and screens into applications in workspaces where the builder has no assigned role, potentially enabling data access or exfiltration through automation webhooks.
Affected context
The issue affects Budibase deployments where authenticated builders can access the resource duplication functionality and the server does not adequately authorize the requested destination workspace. Risk is highest when applications in different workspaces contain sensitive data or permit automations with outbound network access.
Exploit preconditions
- Attack surface: The authenticated
POST /api/resources/duplicateAPI endpoint - Required access: A valid account with builder-level access to Budibase
- Trigger point: A resource duplication request that identifies a destination workspace
- Authorization condition: The account lacks an appropriate role in the destination workspace
- Why exploitation is possible: The endpoint may trust a client-supplied destination workspace identifier without enforcing effective membership or application-level authorization
Why this happens
The vulnerability results from an authorization check that does not adequately bind the requested destination workspace to the authenticated user's permissions. This is a form of CWE-862: Missing Authorization, in which a sensitive operation remains reachable without a required access-control decision. When resource creation or duplication is authorized only by the caller's general builder status, resources may cross workspace boundaries and inherit access to destination applications.
Potential impact
- Unauthorized tables, queries, screens, or automations may be added to another application
- Injected automations could access or alter data within victim applications
- Outgoing webhooks may exfiltrate application data to attacker-controlled services
- Application integrity and workspace isolation may be weakened
- Attackers could create persistence or disruptive workflows within affected applications
General mitigation guidance
Mitigation generally focuses on enforcing authorization at the destination-resource boundary, rather than relying on the caller's broad builder role.
Common defensive patterns include:
- Verify destination workspace and application membership for every duplication request
- Enforce object-level authorization on source and destination resources
- Use secure-by-default denial when workspace ownership, membership, or role information is absent
- Restrict creation of automations, queries, and outbound integrations according to destination permissions
- Apply least privilege to builder accounts and service identities
- Require explicit approval or policy checks for resources capable of external data transmission
- Record and review cross-workspace resource operations
How teams detect issues like this
Organizations can assess this class of issue through:
- Static and policy analysis for endpoints that accept workspace, application, or resource identifiers
- Code review checks confirming authorization occurs after object lookup and before duplication or creation
- Tests that exercise valid users against unauthorized destination workspaces
- API gateway or service policies requiring destination-scope authorization claims
- Audit-log monitoring for unusual cross-workspace duplication and newly created outbound automations
- Automated security testing that checks object-level authorization across tenant and workspace boundaries

