← Back
CVE-2026-54569
critical
CVSS 9.8
Vulnerability in senaite.core (CVE-2026-54569)
Summary
vulnerability in senaite.core (CVE-2026-54569). Successful exploitation can lead to full system takeover. Exploitable via `GET /senaite/bika_setup/`.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-54569** has been found in senaite.core.
Attackers can target a specific entry point like `GET /senaite/bika_setup/` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "senaite.core CVE-2026-54569" on the vendor's site.
CVE-2026-54569 (senaite.core) — CWE-95 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /senaite/bika_setup/ / `eval` / `RecordsField` / `AccessJSONAPI`
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-95) exists in senaite.core. Attackers reach the vulnerable code path via `GET /senaite/bika_setup/` without authentication.
📍 Affected scope
senaite.core — . Attack surface: GET /senaite/bika_setup/ / `eval` / `RecordsField` / `AccessJSONAPI`.
🔥 Severity
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover
🔧 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 `GET /senaite/bika_setup/` requests with malformed payloads or SQL meta-characters. Run `grep -r 'senaite.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 'senaite.core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `senaite.core` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'GET /senaite/bika_setup/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `GET /senaite/bika_setup/` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
7Post-deployment verification verify
Replay attack against GET /senaite/bika_setup/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
senaite.core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]