The PraisonAI Platform API prior to version 0.1.4 contains two critical authorization failures. First, the service layer for issues and projects performs global primary-key lookups without validating workspace ownership, enabling any authenticated user to read, modify, or delete resources in any workspace by swapping UUIDs in API requests. Second, member management endpoints (add, update role, remove) only require a minimum role of "member", allowing any workspace member to promote themselves to owner and remove the original owner. The root cause is that while the route layer verifies workspace membership via the workspace_id in the URL, the service layer ignores workspace scope and caller role level during resource lookups and member operations. The require_workspace_member() dependency functions correctly, but the service layer does not utilize its output properly. These vulnerabilities break workspace isolation and allow unauthorized data access and privilege escalation. The issues are fixed in version 0.1.4 of the PraisonAI Platform API.

An attacker with low-privilege membership in any workspace can exploit these vulnerabilities to access, modify, or delete resources in any workspace by manipulating resource identifiers. They can also escalate their privileges to owner in any workspace they belong to and remove the original owner, effectively taking over the workspace. This results in a complete breach of workspace isolation, leading to high confidentiality, integrity, and availability impacts across all workspaces accessible to the attacker.

Version 0.1.4 of the PraisonAI Platform API patches these authorization bypass issues. Users and administrators should upgrade to version 0.1.4 or later to remediate the vulnerabilities. No other mitigation steps are indicated by the vendor advisory.