Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-73304 medium CVSS 4.9

Information Disclosure in @budibase/server (CVE-2026-73304)

Summary

Vulnerability in @budibase/server (CVE-2026-73304). Confidential information can be exposed externally. Exploitable via GET /api/users/metadata. Mitigation: upgrade to 3.39.25 or later.

Original description

The description as published by the source.

Summary

The /api/users/metadata and /api/users/metadata/:id endpoints in @budibase/server return full global user profiles to any user with POWER role or above. For SSO-authenticated users (OIDC, Google), the response includes oauth2.accessToken and oauth2.refreshToken fields, leaking identity provider credentials to other users who should not have access to them.

Details

When a user authenticates via SSO (OIDC or Google), the OAuth2 tokens are stored in the global CouchDB user document at packages/backend-core/src/auth/auth.ts:170-173:

dbUser.oauth2 = {
  ...dbUser.oauth2,
  ...details,
}
await db.put(dbUser)

The user metadata endpoints are protected by PermissionType.USER, PermissionLevel.READ (packages/server/src/api/routes/user.ts:11), which maps to the POWER permission set (packages/backend-core/src/security/permissions.ts:99).

Path 1 — List all users (GET /api/users/metadata):

  1. controller.fetchMetadata → sdk.users.fetchMetadata() (packages/server/src/sdk/users/utils.ts:78)
  2. → getGlobalUsers() → getRawGlobalUsers() (packages/server/src/utilities/global.ts:101-122) — strips only password and forceResetPassword
  3. → processUser() (packages/server/src/utilities/global.ts:15-76) — strips only password and roles
  4. The oauth2 field containing accessToken and refreshToken is never removed

Path 2 — Single user (GET /api/users/metadata/:id):

  1. controller.findMetadata → `getFullU…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-73304 has been found in @budibase/server.
Attackers can target a specific entry point like GET /api/users/metadata over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 4.9/10.
What to do: upgrade @budibase/server to 3.39.25 or later.
If unsure, ask your IT team or search "@budibase/server CVE-2026-73304" on the vendor's site.

CVE-2026-73304 (@budibase/server) — CWE-200 / CVSS v3 4.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/users/metadata / GET /api/users/metadata/ / oauth2.accessToken / oauth2.refreshToken
Patched: 3.39.25 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Information disclosure (CWE-200) exists in @budibase/server. Attackers reach the vulnerable code path via GET /api/users/metadata.

📍 Affected scope

Check the vendor advisory for the affected versions of @budibase/server. Attack surface: GET /api/users/metadata / GET /api/users/metadata/ / oauth2.accessToken / oauth2.refreshToken.

🔥 Severity

Severity: Medium (CVSS 4.9/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 3.39.25.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual GET /api/users/metadata requests with malformed payloads or SQL meta-characters. Run grep -r '@budibase/server' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r '@budibase/server' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @budibase/server を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'GET /api/users/metadata' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /api/users/metadata への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade @budibase/server to 3.39.25

    ステージング環境で 3.39.25 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against GET /api/users/metadata on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm @budibase/server
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.39.25"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details