Description
Budibase is an open-source low-code platform. Prior to 3.39.25, GET /api/users/metadata and GET /api/users/metadata/:id returned user objects processed by packages/server/src/utilities/global.ts without removing oauth2.accessToken or oauth2.refreshToken. A user with the POWER role could retrieve the identity-provider credentials of SSO-authenticated users and use the refresh tokens for persistent access to connected services. This issue is fixed in version 3.39.25.
Published: 2026-08-13
Score: 4.9 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability lies in the GET /api/users/metadata and GET /api/users/metadata/:id endpoints of Budibase, which return user objects that still contain oauth2.accessToken and oauth2.refreshToken fields. A user with the POWER role can retrieve these broker-level credentials for SSO‑authenticated users. Those tokens allow the attacker to obtain persistent access to connected services, effectively exposing the confidentiality of OAuth credentials. This flaw is categorized as CWE‑200.

Affected Systems

Budibase, version 3.39.x and earlier, uses the packages/server/src/utilities/global.ts code path. Any deployment prior to the 3.39.25 release is affected.

Risk and Exploitability

The CVSS score of 4.9 indicates moderate vulnerability severity. EPSS is not available, and the flaw is not listed in CISA KEV. The attack vector requires a user who already has POWER role privileges, so exploitation is limited to compromised or mis‑role‑assigned accounts. While the impact is significant in terms of credential leakage, the risk is primarily confined to the level of the attacker’s existing privileges.

Generated by OpenCVE AI on August 14, 2026 at 00:28 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Budibase to version 3.39.25 or later, which removes oauth2 access and refresh tokens from metadata responses.
  • Review and limit POWER‑role assignments to trusted administrators to restrict who can retrieve metadata.
  • If an immediate upgrade is not possible, configure access controls so that only administrators can call /api/users/metadata endpoints or manually strip oauth2 fields from responses before delivery.

Generated by OpenCVE AI on August 14, 2026 at 00:28 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-fcrw-f7gg-6g9f Budibase: SSO OAuth2 Token Leakage via User Metadata Endpoints to Power-Role Users
History

Fri, 14 Aug 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Fri, 14 Aug 2026 00:00:00 +0000

Type Values Removed Values Added
First Time appeared Budibase
Budibase budibase
Vendors & Products Budibase
Budibase budibase

Thu, 13 Aug 2026 22:15:00 +0000

Type Values Removed Values Added
Description Budibase is an open-source low-code platform. Prior to 3.39.25, GET /api/users/metadata and GET /api/users/metadata/:id returned user objects processed by packages/server/src/utilities/global.ts without removing oauth2.accessToken or oauth2.refreshToken. A user with the POWER role could retrieve the identity-provider credentials of SSO-authenticated users and use the refresh tokens for persistent access to connected services. This issue is fixed in version 3.39.25.
Title Budibase: SSO OAuth2 Token Leakage via User Metadata Endpoints to Power-Role Users
Weaknesses CWE-200
References
Metrics cvssV3_1

{'score': 4.9, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N'}


Subscriptions

Budibase Budibase
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-08-14T15:09:18.395Z

Reserved: 2026-08-11T19:42:11.451Z

Link: CVE-2026-73304

cve-icon Vulnrichment

Updated: 2026-08-14T15:09:13.599Z

cve-icon NVD

Status : Received

Published: 2026-08-13T22:17:25.500

Modified: 2026-08-14T16:17:00.100

Link: CVE-2026-73304

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-14T00:30:03Z

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor