← Back
CVE-2026-52888
medium
CVSS 6.8
Vulnerability in @nocobase/plugin-collection-sql (CVE-2026-52888)
Summary
vulnerability in @nocobase/plugin-collection-sql (CVE-2026-52888). Confidential information can be exposed externally. Exploitable via `POST /api/sqlCollection`. Mitigation: upgrade to `2.1.0-beta.45` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-52888** has been found in @nocobase/plugin-collection-sql.
Attackers can target a specific entry point like `POST /api/sqlCollection` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.8/10.
What to do: upgrade @nocobase/plugin-collection-sql to **2.1.0-beta.45** or later.
If unsure, ask your IT team or search "@nocobase/plugin-collection-sql CVE-2026-52888" on the vendor's site.
CVE-2026-52888 (@nocobase/plugin-collection-sql) — CWE-184 / CVSS v3 6.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/sqlCollection / `pg_shadow` / `pg_roles` / `pg_stat_activity`
Patched: `2.1.0-beta.45` — 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-184) exists in @nocobase/plugin-collection-sql. Attackers reach the vulnerable code path via `POST /api/sqlCollection` without authentication.
📍 Affected scope
@nocobase/plugin-collection-sql — . Attack surface: POST /api/sqlCollection / `pg_shadow` / `pg_roles` / `pg_stat_activity`.
🔥 Severity
Severity: Medium (CVSS 6.8/10). Confidential information can be exposed externally
🔧 How to fix
Update to **2.1.0-beta.45**.
🛡️ 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/sqlCollection` requests with malformed payloads or SQL meta-characters. Run `grep -r '@nocobase/plugin-collection-sql' .` 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 '@nocobase/plugin-collection-sql' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@nocobase/plugin-collection-sql` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /api/sqlCollection' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /api/sqlCollection` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade @nocobase/plugin-collection-sql to 2.1.0-beta.45ステージング環境で 2.1.0-beta.45 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against POST /api/sqlCollection on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@nocobase/plugin-collection-sql
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.0-beta.45"}]}]
References
- web https://github.com/nocobase/nocobase/commit/87c548969ce9258dd7f0d9571c9453ae10bc3fc4
- web https://github.com/nocobase/nocobase/releases/tag/v2.1.0-alpha.46
- web https://github.com/nocobase/nocobase/security/advisories/GHSA-v8vm-cqh8-q87q
- web https://nvd.nist.gov/vuln/detail/CVE-2026-52888
- web https://github.com/nocobase/nocobase/pull/9683
- web https://github.com/nocobase/nocobase/commit/4aecb60d151a9002004dcf984f63d62f17a6cb45
- web https://github.com/nocobase/nocobase/releases/tag/v2.0.62
- web https://github.com/advisories/GHSA-v8vm-cqh8-q87q