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