← Back
GHSA-pvcr-8mvp-w8qr
Vulnerability in @budibase/server (GHSA-pvcr-8mvp-w8qr)
Summary
vulnerability in @budibase/server (GHSA-pvcr-8mvp-w8qr). Risk of unauthorized operations or information disclosure. Exploitable via `POST /api/chat-links/`.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-pvcr-8mvp-w8qr** has been found in @budibase/server.
Attackers can target a specific entry point like `POST /api/chat-links/` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "@budibase/server GHSA-pvcr-8mvp-w8qr" on the vendor's site.
GHSA-pvcr-8mvp-w8qr (@budibase/server) — CWE-285 /
Attack surface: POST /api/chat-links/ / GET /api/chat-links/ / POST /api/agent/ / POST /api/chat-links/.../handoff
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-285) exists in @budibase/server. Attackers reach the vulnerable code path via `POST /api/chat-links/` without authentication.
📍 Affected scope
@budibase/server — . Attack surface: POST /api/chat-links/ / GET /api/chat-links/ / POST /api/agent/ / POST /api/chat-links/.../handoff.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ 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/chat-links/` 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 (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@budibase/server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@budibase/server` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /api/chat-links/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /api/chat-links/` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
7Post-deployment verification verify
Replay attack against POST /api/chat-links/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@budibase/server
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
References
- web https://github.com/Budibase/budibase/security/advisories/GHSA-pvcr-8mvp-w8qr
- web https://github.com/Budibase/budibase/pull/19194
- web https://github.com/Budibase/budibase/commit/362e6c654fb4da6e123c734333da2d6cbdcdb7ef
- web https://github.com/Budibase/budibase/releases/tag/3.39.30
- web https://github.com/advisories/GHSA-pvcr-8mvp-w8qr