Budibase: Creator Can Impersonate Tenant Admin or Owner

Summary

A creator-level user on Budibase can make changes to user roles and accounts, potentially taking control of the entire tenant. This is a serious security risk because it allows an unauthorized user to make significant changes. To stay safe, Budibase administrators should review their user roles and permissions, and ensure that all actions are properly validated and authorized.

What to do

No fix is available yet. Check with your software vendor for updates.

Affected software

Vendor	Product	Affected versions	Fix available
budibase	budibase	<= 3.32.3	–

Original title

Budibase is a low code platform for creating internal tools, workflows, and admin panels. This issue is a combination of Vertical Privilege Escalation and IDOR (Insecure Direct Object Reference) du...

Original description

Budibase is a low code platform for creating internal tools, workflows, and admin panels. This issue is a combination of Vertical Privilege Escalation and IDOR (Insecure Direct Object Reference) due to missing server-side RBAC checks in the /api/global/users endpoints. A Creator-level user, who should have no permissions to manage users or organizational roles, can instead promote an App Viewer to Tenant Admin, demote a Tenant Admin to App Viewer, or modify the Owner’s account details and all orders (e.g., change name). This is because the API accepts these actions without validating the requesting role, a Creator can replay Owner-only requests using their own session tokens. This leads to full tenant compromise.

nvd CVSS4.0 8.7

Vulnerability type

CWE-862 Missing Authorization

https://github.com/Budibase/budibase/security/advisories/GHSA-2g39-332f-68p9