← Back
CVE-2026-55410
medium
CVSS 6.7
OS Command Injection in @nocobase/plugin-backups (CVE-2026-55410)
Summary
OS command injection in @nocobase/plugin-backups (CVE-2026-55410). Data can be tampered with by attackers. Exploitable via ``database.schema``. Mitigation: upgrade to `2.1.19` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-55410** has been found in @nocobase/plugin-backups.
Attackers can target a specific entry point like ``database.schema`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.7/10.
What to do: upgrade @nocobase/plugin-backups to **2.1.19** or later.
If unsure, ask your IT team or search "@nocobase/plugin-backups CVE-2026-55410" on the vendor's site.
CVE-2026-55410 (@nocobase/plugin-backups) — CWE-78 / CVSS v3 6.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `database.schema` / `e03d267362b3426f484c28783020b4a2a08911e8` / `backup` / `force`
Patched: `2.1.19` — 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
**OS command injection** (CWE-78) exists in @nocobase/plugin-backups. Attackers reach the vulnerable code path via ``database.schema`` without authentication.
📍 Affected scope
@nocobase/plugin-backups — . Attack surface: `database.schema` / `e03d267362b3426f484c28783020b4a2a08911e8` / `backup` / `force`.
🔥 Severity
Severity: Medium (CVSS 6.7/10). Data can be tampered with by attackers
🔧 How to fix
Update to **2.1.19**.
🛡️ 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 request patterns matching this CVE's known IOCs. Run `grep -r '@nocobase/plugin-backups' .` 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-backups' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@nocobase/plugin-backups` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @nocobase/plugin-backups to 2.1.19ステージング環境で 2.1.19 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@nocobase/plugin-backups
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.19"}]}]
References
- web https://github.com/nocobase/nocobase/commit/0e1aba1b7b112ffc841588963f7343c00edd9806
- web https://github.com/nocobase/nocobase/releases/tag/v2.1.19
- web https://github.com/nocobase/nocobase/security/advisories/GHSA-p853-83gj-wjj3
- web https://nvd.nist.gov/vuln/detail/CVE-2026-55410
- web https://github.com/advisories/GHSA-p853-83gj-wjj3