# CVE-2026-25045: Budibase Critical Privilege Escalation & IDOR via Missing RBAC on User Role Management (Creator-Role)

> Attackers with Creator roles can escalate privileges to Tenant Admin or modify Owner accounts due to missing server-side RBAC checks in user management APIs.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Mar 2026
- **Updated:** 9 Mar 2026
- **Also known as:** GHSA-2g39-332f-68p9

## What is CVE-2026-25045?

CVE-2026-25045 is a high-severity missing authorization vulnerability in budibase, published on 9 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-25045?

It affects 1 product.


Products: Budibase Budibase.

## How do I fix CVE-2026-25045?

No fix has been published for CVE-2026-25045 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-25045 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25045 exists.

## Other vulnerabilities in budibase

- [CVE-2026-54350](https://insights.sbomify.com/CVE-2026-54350/): Budibase: Anonymous NoSQL operator injection via published-app query templates (critical 10.0)
- [CVE-2026-27702](https://insights.sbomify.com/CVE-2026-27702/): Budibase Vulnerable to Remote Code Execution via Unsafe eval() in View Filter Map Function (Budibase Cloud) (critical 9.9)
- [CVE-2026-54352](https://insights.sbomify.com/CVE-2026-54352/): Budibase: Arbitrary file read by workspace-builder via PWA-zip symlink upload (critical 9.6)
- [CVE-2026-31818](https://insights.sbomify.com/CVE-2026-31818/): Budibase: Server-Side Request Forgery via REST Connector with Empty Default Blacklist (critical 9.6)
- [CVE-2026-30240](https://insights.sbomify.com/CVE-2026-30240/): Budibase PWA ZIP Upload Path Traversal Allows Reading Arbitrary Server Files Including All Environment Secrets (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25045 and fix it if it is affected.

What it is: CVE-2026-25045 is a high-severity missing authorization vulnerability in budibase, published on 9 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25045 exists.

Affected product: budibase. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25045/ (Markdown: https://insights.sbomify.com/CVE-2026-25045/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25045
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25045
- OSV: https://osv.dev/vulnerability/CVE-2026-25045

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25045/
Summaries are generated and may contain mistakes; the official description above is the record.