Budibase title matches expose a low-code access review target
Budibase can connect to internal data, generate applications, and expose published apps to end users. A public Budibase deployment may therefore contain a builder, a portal, and several applications with different data permissions.
A count-only ZoomEye query on 2026-11-03 at 18:44:30 UTC found 4,000 matches for title="Budibase" with sub_type=all, page 1, and a page size of 1. The application query app="Budibase" returned 3,681 at 18:44:31 UTC. The close result sizes are useful for comparison, but the count does not establish whether a matched instance is production or test.
title="Budibase"
Budibase documentation describes tenant roles and workspace roles. Organisation admins manage global settings and users, Creators can build in assigned workspaces, and end users can use published apps without builder access. The documentation also notes that app roles can control screens and data, and that a custom app role can inherit a higher role. Those inheritance rules are a useful review point because a role that looks limited may still see more than expected.
The title query may find a login portal, a published app, documentation, or a custom page that reuses the product name. Verify the component before testing permissions. Then determine whether local passwords, OIDC, or another SSO path is active. Budibase's OIDC documentation discusses email verification and account linking, including a setting that can allow unverified email linking. That setting should be an explicit policy decision.
Review checks include:
- Map tenant roles, workspace access, groups, and app roles.
- Confirm whether enforced SSO is available and enabled where required.
- Review OIDC issuer, subject, email verification, and account-linking settings.
- Inventory external data sources and confirm that credentials remain server side.
- Search for public apps with sensitive queries or broad role inheritance.
- Review audit logs and remove inactive users or obsolete workspaces.
The exact ZoomEye search result provides a reproducible candidate set. The operator should compare it with owned domains and then inspect the application boundary under an authorized process. A low-code platform can accelerate internal tools, and it also concentrates authority in a small number of builders and data connections.
Test role inheritance with real access paths
Role inheritance is easier to describe than to verify. Budibase documentation says a higher role can see content available to lower roles and that a group can grant a higher permission than a direct assignment. An administrator should test the path that a real user receives through a group, not only the role shown on the individual record.
Use at least three accounts: an organisation administrator, a creator assigned to one workspace, and an end user with a specific app role. Confirm which workspaces and screens each account can reach. Then add the end user to a group and repeat the test. The result should match the intended highest-permission rule and should produce an audit event for the access change.
The OIDC path adds identity claims and account linking to the same test. Confirm that email verification is required and that an unverified identity cannot link to an existing account unless the organization deliberately enabled that behavior. A low-code platform scales internal app creation quickly. The access review has to scale with the same speed, or the role model becomes a source of hidden authority.
Top comments (0)