CVE-2026-47413: praisonai-platform: Any workspace member can add arbitrary user as owner via POST /workspaces/{id}/members
PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Versions prior to 0.1.4 have aprivilege escalation / cross-tenant member injection. The `POST /workspaces/{workspace_id}/members` endpoint is gated only by `require_workspace_member(workspace_id)` (default `min_role="member"`) and forwards the request body's `user_id` and `role` straight into `MemberService.add(workspace_id, user_id, role)`, which has no caller-permission check. A user with the lowest workspace privilege can add any user (including a new attacker-controlled second account, or an existing account they want to grief) as owner of the workspace. PraisonAI Platform version 0.1.4 patches the issue.
Security readout for executives and security teams
Plain-English summary
A low-privileged PraisonAI Platform workspace member could promote any user to workspace owner. That can let an insider or compromised member account take control of a workspace and access or alter its contents. The vendor states versions before 0.1.4 are affected and 0.1.4 patches the issue.
Executive priority
Treat as urgent for any production or shared PraisonAI Platform deployment. A regular member account could become an owner, creating a practical path to workspace takeover and data exposure. Prioritize patching and membership review over routine backlog handling.
Technical view
The member-add endpoint accepted user_id and role from the request body after only confirming the caller was a workspace member. MemberService.add did not enforce a stronger caller permission check, enabling privilege escalation and cross-tenant member injection to owner role. CVSS 9.6 reflects network access, low privileges, no user interaction, and changed scope.
Likely exposure
Exposure is limited to deployments running PraisonAI Platform versions earlier than 0.1.4 where untrusted or compromised users have member access to workspaces.
Exploitation context
The source bundle does not show KEV listing or active exploitation evidence. The issue is still high urgency because exploitation requires only a normal workspace member account and targets authorization logic, not complex memory corruption.
Researcher notes
Evidence comes from the CVE source bundle, GitHub advisory, and referenced commit. The bundle names the vulnerable endpoint and missing authorization boundary, but does not provide active exploitation evidence, public exploit evidence, or additional mitigations beyond the fixed 0.1.4 release.
Mitigation direction
Upgrade PraisonAI Platform to version 0.1.4 or later.
Review vendor advisory and patch notes before deployment.
Restrict workspace membership to trusted users until upgraded.
Audit workspace owners and recent member additions.
Remove unexpected owners or members after investigation.
Check vendor guidance for any additional hardening steps.
Validation and detection
Inventory PraisonAI Platform versions across all environments.
Confirm no instance runs a version earlier than 0.1.4.
Review access controls for workspace member-management routes.
Verify owner assignment requires an authorized owner or administrator.
Audit logs for unusual member additions or owner promotions.
Check production workspaces for unexpected external accounts.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-269: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-269 · source CWE mapping
Improper Privilege Management
Improper Privilege Management represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.