Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-47409 high CVSS 8.1

Privilege Escalation in praisonai-platform (CVE-2026-47409)

Summary

Vulnerability in praisonai-platform (CVE-2026-47409). Data can be tampered with by attackers. Exploitable via DELETE /workspaces/{workspace_id}/members/{user_id}. Mitigation: upgrade to 0.1.4 or later.

Original description

The description as published by the source.

Summary

Type: Authorization bypass enabling owner lockout. The DELETE /workspaces/{workspace_id}/members/{user_id} endpoint is gated only by require_workspace_member(workspace_id) (default min_role="member"). Any member can remove any other member, including the workspace owner, using a single DELETE. There is no caller-role check, no target-role check, no "cannot remove last owner" guard.
File: src/praisonai-platform/praisonai_platform/api/routes/workspaces.py, lines 130-140; services/member_service.py, lines 71-78.
Root cause: MemberService.remove(workspace_id, user_id) performs the deletion without any caller-permission check or owner-protection logic. The route accepts the URL-supplied user_id and dispatches it straight through. The role hierarchy (MemberService.has_role) is implemented but never invoked here. A member-tier attacker can issue DELETE .../members/ and immediately lock the legitimate owner out of the workspace.

Affected Code

File 1: src/praisonai-platform/praisonai_platform/api/routes/workspaces.py, lines 130-140.

@router.delete("/{workspace_id}/members/{user_id}", status_code=status.HTTP_204_NO_CONTENT)
async def remove_member(
    workspace_id: str,
    user_id: str,
    user: AuthIdentity = Depends(require_workspace_member),         # <-- BUG: defaults to min_role="member"
    session: AsyncSession = Depends(get_db),
):
    member_svc = MemberService(session)
    removed = await member_svc.remove(wor…

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-47409 has been found in praisonai-platform.
Attackers can target a specific entry point like DELETE /workspaces/{workspace_id}/members/{user_id} over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 8.1/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-47409" on the vendor's site.

CVE-2026-47409 (praisonai-platform) — CWE-269 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: DELETE /workspaces/{workspace_id}/members/{user_id} / GET /workspaces/W/members / DELETE /workspaces/W/members/O_id / GET /workspaces/W/...
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-269) exists in praisonai-platform. Attackers reach the vulnerable code path via DELETE /workspaces/{workspace_id}/members/{user_id}.

📍 Affected scope

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

🔥 Severity

Severity: High (CVSS 8.1/10). Data can be tampered with by attackers.

🔧 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 DELETE /workspaces/{workspace_id}/members/{user_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 'DELETE /workspaces/{workspace_id}/members/{user_id}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで DELETE /workspaces/{workspace_id}/members/{user_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 DELETE /workspaces/{workspace_id}/members/{user_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