Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-47405 high CVSS 8.8

Vulnerability in praisonai-platform (CVE-2026-47405)

Summary

Vulnerability in praisonai-platform (CVE-2026-47405). Successful exploitation can lead to full system takeover. Exploitable via PATCH /workspaces/{workspace_id}. Mitigation: upgrade to 0.1.4 or later.

Original description

The description as published by the source.

Summary

PraisonAI Platform has a broken workspace authorization check that allows any authenticated low-privilege workspace member to escalate their own role to owner.

The issue is caused by privileged workspace-management routes using the shared dependency require_workspace_member(...) without requiring admin or owner. The dependency defaults to min_role="member", so routes that should be administrative are accessible to ordinary workspace members.

As a result, a normal workspace member can:

  • promote their own account from member to owner;
  • add arbitrary users as owner or admin;
  • change other members' roles;
  • remove legitimate owners or members;
  • take over workspace membership completely;
  • perform destructive workspace operations after escalation.

This is a broken access control / vertical privilege escalation vulnerability.

Details

The vulnerable authorization dependency is defined in:

praisonai_platform/api/deps.py

The dependency defaults to the lowest workspace role:

async def require_workspace_member(
    workspace_id: str,
    user: AuthIdentity = Depends(get_current_user),
    session: AsyncSession = Depends(get_db),
    min_role: str = "member",
) -> AuthIdentity:
    ...
    has = await member_svc.has_role(workspace_id, user.id, min_role)

Because min_role defaults to "member", any route using:

Depends(require_workspace_member)

without explicitly passing a stronger role only requ…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-47405 has been found in praisonai-platform.
Attackers can target a specific entry point like PATCH /workspaces/{workspace_id} over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.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-47405" on the vendor's site.

CVE-2026-47405 (praisonai-platform) — CWE-284 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PATCH /workspaces/{workspace_id} / DELETE /workspaces/{workspace_id} / POST /workspaces/{workspace_id}/members / PATCH /workspaces/{workspace_id}/members/{user_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-284) exists in praisonai-platform. Attackers reach the vulnerable code path via PATCH /workspaces/{workspace_id}.

📍 Affected scope

Check the vendor advisory for the affected versions of praisonai-platform. Attack surface: PATCH /workspaces/{workspace_id} / DELETE /workspaces/{workspace_id} / POST /workspaces/{workspace_id}/members / PATCH /workspaces/{workspace_id}/members/{user_id}.

🔥 Severity

Severity: High (CVSS 8.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 PATCH /workspaces/{workspace_id} 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'praisonai-platform' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で praisonai-platform を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'PATCH  /workspaces/{workspace_id}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで PATCH /workspaces/{workspace_id} への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade praisonai-platform to 0.1.4

    ステージング環境で 0.1.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against PATCH  /workspaces/{workspace_id} on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

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"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details