PraisonAI has Cross-Workspace IDOR and Privilege Escalation via Platform API

Summary

PraisonAI is a multi-agent teams system. Versions prior to 0.1.4 of the PraisonAI Platform API have two authorization failures that together break workspace isolation. The service layer for issues and projects performs global primary-key lookups without checking workspace ownership, so any authenticated user can read, modify, and delete resources in any workspace just by swapping UUIDs in their API requests. On top of that, every member management endpoint (add, update role, remove) only requires `min_role="member"`, which lets any workspace member promote themselves to owner and kick out the original owner. A low-privilege member of one workspace can steal data from every other workspace and take over any workspace they belong to. Both issues come from the same gap: the route layer pulls `workspace_id` from the URL and verifies membership, but the service layer ignores the workspace scope for resource lookups and ignores the caller's role level for member operations. The `require_workspace_member()` dependency does its job correctly. The problem is that the service layer doesn't use the information it provides. Version 0.1.4 of the PraisonAI Platform API patch the issue.

Timeline

1. Aug 7, 2026, 9:22 PM UTCCVE published
2. Aug 11, 2026, 1:16 AM UTCCISA SSVC assessment

   Exploitation: poc · Automatable: no · Technical impact: total

3. Aug 11, 2026, 1:17 AM UTCRecord last updated

Affected versions

• MervinPraison praisonai-platform

  fixed in 0.1.4

• praisonai-platformPyPI

  fixed in 0.1.4

References 2