CVE-2026-47407: PraisonAI Platform has a cross-workspace IDOR + member-role privilege escalation
PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Prior to version 0.1.4, the Platform server exposes resources under `/api/v1/workspaces/{workspace_id}/...` and protects them with a `require_workspace_member(workspace_id)` FastAPI dependency. The dependency only checks that the caller is a member of the workspace_id in the URL prefix. The route handlers then look up the inner resource (`agent_id`, `issue_id`, `project_id`, `label_id`, `comment_id`, `dependency_id`) by primary key alone. The resource's own `workspace_id` is never compared to the URL's `workspace_id`. A user can therefore put their own workspace in the URL prefix and any other workspace's resource ID in the path. The auth check passes, since they really are a member of the prefix workspace. The service then returns the cross-tenant resource for read, update, or delete. There is a second bug in the member-management routes (`add_member`, `update_member_role`, `remove_member`, `update_workspace`, `delete_workspace`). Each one inherits the default `min_role="member"` from `require_workspace_member`. Any basic member can therefore promote themselves to admin or owner, demote or remove other members, and delete the workspace. The role hierarchy exists in the schema but is not enforced. Registration is open at `/api/v1/auth/register` with no email verification. The default server bind is `0.0.0.0:8000` (`python -m praisonai_platform`). One curl from any unauthenticated network position is enough to bootstrap into the system. PraisonAI Platform version 0.1.4 patches the issue.
Security readout for executives and security teams
Plain-English summary
PraisonAI Platform before 0.1.4 can let an ordinary workspace member access or change another workspace’s resources and elevate their own role. In a multi-tenant system, this creates a serious risk of tenant data exposure, unauthorized changes, and workspace takeover.
Executive priority
Treat this as an immediate remediation item for any production or shared PraisonAI Platform deployment. The main business risk is tenant boundary failure: users may access or control workspaces they should not be able to reach.
Technical view
The workspace membership check validates only the workspace ID in the URL prefix. Handlers then fetch inner objects by primary key without confirming each object belongs to that workspace. Member-management routes also use a default member-level authorization requirement, allowing basic members to change roles and workspace state.
Likely exposure
Organizations running PraisonAI Platform versions earlier than 0.1.4 are affected. Exposure is higher where the Platform server is reachable by untrusted networks, because registration is described as open and no email verification is noted in the source bundle.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The issue is still high urgency because exploitation requires only low privileges, no user interaction, and can affect confidentiality, integrity, and availability across tenants.
Researcher notes
Focus review on object-level authorization and role enforcement. The patch is identified as 0.1.4 with linked PR and commit evidence. Do not assume exploitation in the wild from the supplied evidence; KEV is false in the bundle.
Mitigation direction
Upgrade PraisonAI Platform to version 0.1.4 or later.
Restrict Platform server access to trusted networks until upgraded.
Review and tighten registration controls where vendor-supported.
Audit workspace membership and ownership for unexpected changes.
Follow the GitHub advisory for any additional vendor guidance.
Validation and detection
Inventory PraisonAI Platform deployments and confirm versions are 0.1.4 or later.
Review whether any Platform servers are internet-facing or broadly reachable.
Check logs for unexpected registrations, role changes, removals, updates, or workspace deletions.
Audit for unusual cross-workspace access to agents, projects, issues, labels, comments, or dependencies.
Confirm member-management routes require appropriate elevated roles after patching.
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.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-863: 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.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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
4Source 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.
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.