Server: Budibase: Privilege escalation via public role assignment API missing app-level authorization
Budibase version 3.39.19 and earlier (up to 3.38.1) contains a privilege escalation vulnerability in its public role-assignment API. An app-scoped builder user, who should only have builder access to specific apps, can exploit this flaw to assign themselves builder or admin roles on any app within the tenant. This occurs because the API fails to properly authorize app-level role assignments, only validating global role flags. As a result, attackers can gain unauthorized access to other apps, violating intended app isolation boundaries.
AI Analysis
Technical Summary
Budibase versions up to 3.38.1 suffer from a missing authorization check in the public role-assignment API endpoint POST /api/public/v1/roles/assign. The endpoint validates only global role flags ('admin' and 'builder') but does not verify whether the caller has permission to assign app-scoped roles such as 'appBuilder' or arbitrary data-plane roles within specific apps. An attacker with app-scoped builder privileges on one app can exploit this by calling the endpoint with their own app ID in the header and specifying other apps in the role assignment payload, thereby granting themselves elevated roles on any app in the tenant. This flaw arises from an incomplete fix that only hardened global role validation, leaving app-level role assignments unchecked. The vulnerability allows crossing the security boundary from limited app builder access to full builder or admin access on any app, enabling unauthorized data access, configuration changes, and automation edits.
Potential Impact
An attacker with app-scoped builder privileges on a single app can escalate their privileges to become a builder or admin on any other app within the same tenant. This breaks the intended isolation between apps, allowing unauthorized read and modification of data, access to datasource configurations including credentials, and the ability to alter automations and execute arbitrary scripts. The compromise affects confidentiality, integrity, and availability of all apps in the tenant. The vulnerability requires only low attack complexity and no user interaction, making it a high-severity risk.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict app-scoped builder roles carefully and monitor for suspicious role-assignment API usage. Avoid exposing the public role-assignment API to untrusted users. Review and harden authorization logic to ensure app-level role assignments require verification that the caller controls the target app. Follow vendor updates for a security patch addressing this missing authorization check.
Server: Budibase: Privilege escalation via public role assignment API missing app-level authorization
Description
Budibase version 3.39.19 and earlier (up to 3.38.1) contains a privilege escalation vulnerability in its public role-assignment API. An app-scoped builder user, who should only have builder access to specific apps, can exploit this flaw to assign themselves builder or admin roles on any app within the tenant. This occurs because the API fails to properly authorize app-level role assignments, only validating global role flags. As a result, attackers can gain unauthorized access to other apps, violating intended app isolation boundaries.
CVSS v3.1
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Budibase versions up to 3.38.1 suffer from a missing authorization check in the public role-assignment API endpoint POST /api/public/v1/roles/assign. The endpoint validates only global role flags ('admin' and 'builder') but does not verify whether the caller has permission to assign app-scoped roles such as 'appBuilder' or arbitrary data-plane roles within specific apps. An attacker with app-scoped builder privileges on one app can exploit this by calling the endpoint with their own app ID in the header and specifying other apps in the role assignment payload, thereby granting themselves elevated roles on any app in the tenant. This flaw arises from an incomplete fix that only hardened global role validation, leaving app-level role assignments unchecked. The vulnerability allows crossing the security boundary from limited app builder access to full builder or admin access on any app, enabling unauthorized data access, configuration changes, and automation edits.
Potential Impact
An attacker with app-scoped builder privileges on a single app can escalate their privileges to become a builder or admin on any other app within the same tenant. This breaks the intended isolation between apps, allowing unauthorized read and modification of data, access to datasource configurations including credentials, and the ability to alter automations and execute arbitrary scripts. The compromise affects confidentiality, integrity, and availability of all apps in the tenant. The vulnerability requires only low attack complexity and no user interaction, making it a high-severity risk.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict app-scoped builder roles carefully and monitor for suspicious role-assignment API usage. Avoid exposing the public role-assignment API to untrusted users. Review and harden authorization logic to ensure app-level role assignments require verification that the caller controls the target app. Follow vendor updates for a security patch addressing this missing authorization check.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-j9fc-w3mr-x6mv
- Osv Schema Version
- 1.4.0
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a6542309c2644c7f808a772
Added to database: 07/25/2026, 23:09:36 UTC
Last enriched: 07/25/2026, 23:58:00 UTC
Last updated: 07/26/2026, 00:20:08 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.