← Back
CVE-2026-48147
medium
CVSS 6.5
Vulnerability in @budibase/backend-core (CVE-2026-48147)
Summary
vulnerability in @budibase/backend-core (CVE-2026-48147). Data can be tampered with by attackers. Exploitable via `POST /api/global/users/invite`. Mitigation: upgrade to `3.35.4` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-48147** has been found in @budibase/backend-core.
Attackers can target a specific entry point like `POST /api/global/users/invite` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade @budibase/backend-core to **3.35.4** or later.
If unsure, ask your IT team or search "@budibase/backend-core CVE-2026-48147" on the vendor's site.
CVE-2026-48147 (@budibase/backend-core) — CWE-185 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: POST /api/global/users/invite / `ctx.request.url` / `buildMatcherRegex` / `true`
Patched: `3.35.4` — 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
**A vulnerability** (CWE-185) exists in @budibase/backend-core. Attackers reach the vulnerable code path via `POST /api/global/users/invite` without authentication.
📍 Affected scope
@budibase/backend-core — . Attack surface: POST /api/global/users/invite / `ctx.request.url` / `buildMatcherRegex` / `true`.
🔥 Severity
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers
🔧 How to fix
Update to **3.35.4**.
🛡️ 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 `POST /api/global/users/invite` requests with malformed payloads or SQL meta-characters. Run `grep -r '@budibase/backend-core' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@budibase/backend-core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@budibase/backend-core` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /api/global/users/invite' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /api/global/users/invite` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade @budibase/backend-core to 3.35.4ステージング環境で 3.35.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against POST /api/global/users/invite on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@budibase/backend-core
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.35.4"}]}]