LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25040: Budibase Vulnerable to Privilege Escalation via API Abuse – Creator Can Invite Users with Admin/Any Role

Budibase is a low code platform for creating internal tools, workflows, and admin panels. In versions up to and including 3.26.3, a Creator-level user, who normally has no UI permission to invite users, can manipulate API requests to invite new users with any role, including Admin, Creator, or App Viewer, and assign them to any group in the organization. This allows full privilege escalation, bypassing UI restrictions, and can lead to complete takeover of the workspace or organization. As of time of publication, no known fixed versions are available.

MediumCVSS 5.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Budibase versions up to 3.26.3 allow a lower-privileged Creator user to bypass UI limits and invite users with higher roles, including Admin. This can let an insider or compromised Creator account take over a workspace or organization. Sources state no fixed version was available at publication.

Executive priority

Prioritize if Budibase manages sensitive internal tools or many users have Creator access. The immediate business risk is unauthorized administrative control after a Creator account is misused or compromised. Treat as a governance and access-control issue requiring near-term review.

Technical view

CVE-2026-25040 is an improper authorization issue (CWE-863) in Budibase. A Creator-level account can abuse invite-related API behavior to assign arbitrary roles and groups. The CVSS 4.0 score is 5.7, with low attack complexity and required low privileges. Impact is primarily integrity within the Budibase organization.

Likely exposure

Organizations running Budibase 3.26.3 or earlier are exposed if untrusted, numerous, or compromised Creator accounts exist. Internet exposure increases account-compromise risk, but exploitation still requires valid Creator-level privileges according to the CVE description.

Exploitation context

The issue is not listed in CISA KEV, and the provided sources do not confirm active exploitation. A public proof-of-concept reference is included in the CVE materials, so defenders should assume the behavior is reproducible without treating it as confirmed in-the-wild abuse.

Researcher notes

Evidence is limited to the CVE record and referenced advisory materials. The reported weakness is API authorization bypass versus UI permission enforcement. Do not infer affected hosted tiers, deployment models, or a fixed version beyond what the sources state.

Mitigation direction

  • Check Budibase’s advisory for newly released fixed versions or official mitigations.
  • Limit Creator role membership to trusted users until patched.
  • Review and tighten who can invite users or manage groups.
  • Monitor for unexpected user invitations, role changes, and group assignments.
  • Consider compensating controls around SSO, MFA, and account lifecycle governance.

Validation and detection

  • Inventory Budibase deployments and record exact versions.
  • Identify workspaces running Budibase 3.26.3 or earlier.
  • Audit all Creator accounts for business need and ownership.
  • Review recent invitation, role, and group assignment activity.
  • Confirm whether vendor guidance or a fixed release is now available.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-863: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-25040 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.7 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.7CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

5.7Medium
CVSS 4.0 vector shape for CVE-2026-25040Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Budibasebudibase<= 3.26.3Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-863 · source CWE mapping

Incorrect Authorization

Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.