Security readout for executives and security teams
Plain-English summary
Budibase versions before 3.39.30 can incorrectly treat an unverified email from an OIDC identity provider as proof of account ownership. A newly authenticated identity may therefore be attached to another user’s account, granting the attacker that user’s roles and access. The issue can compromise confidentiality, integrity, and availability.
Executive priority
Treat as an urgent identity-security update for any affected OIDC-enabled deployment. Account takeover could grant the victim’s roles and affect sensitive applications or administrative functions. Patch promptly, then review identity links and authentication evidence. Deployments without OIDC still require version confirmation, but the described attack path depends on configured OIDC SSO.
Technical view
The OIDC middleware resolved email without requiring email_verified. Budibase’s SSO logic then used the email as a fallback account-linking key through users.getGlobalUserByEmail. Under a configured provider capable of asserting an unverified victim email, a new provider identity could merge into the victim’s global account. Version 3.39.30 fixes the issue.
Likely exposure
Exposure is limited to Budibase deployments below 3.39.30 using OIDC SSO. Practical risk depends on whether a configured identity provider permits an attacker to authenticate while asserting another person’s email as unverified. The supplied evidence does not identify specific providers or deployment configurations meeting that condition.
Exploitation context
Exploitation requires authentication through a configured identity provider and the ability to present a victim’s email without verification. No user interaction is required after those conditions are met. The bundle marks KEV as false and provides no evidence of active exploitation, public weaponization, or observed attacks.
Researcher notes
CWE-287 applies because account identity was accepted without adequate verification. CVSS 4.0 is 9.0 with network reachability, low complexity, low privileges, no user interaction, and high downstream impacts. The attack includes a prerequisite condition, represented by AT:P. The bundle establishes the vulnerable data flow and fix, but not real-world exploitation prevalence.
Mitigation direction
- Upgrade Budibase to version 3.39.30 or later.
- Prioritize deployments using OIDC SSO and hosting privileged accounts.
- Confirm identity providers require verified, authoritative email claims.
- Consult the Budibase advisory for any additional vendor guidance.
Validation and detection
- Inventory Budibase versions and identify deployments below 3.39.30.
- Determine which deployments have OIDC SSO configured.
- Verify each provider’s handling of email and email_verified claims.
- Review identity mappings for unexpected provider identities linked to existing users.
- Inspect available authentication records for suspicious account linking or inherited roles.
- After upgrading, confirm the deployed version is 3.39.30 or later.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-287: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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 lookupCVE-2026-73302 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
9CriticalVector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Budibase/budibase/security/advisories/GHSA-hp6v-6jw7-gv2fCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/Budibase/budibase/pull/19173CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/Budibase/budibase/commit/9ecd0048d9c3ae0ee9bd0e6204c621794dd1a4d3CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/Budibase/budibase/releases/tag/3.39.30CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Authentication
Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.