CVE-2026-47418
Deferred Deferred - Pending Action

Insecure Direct Object Reference in PraisonAI Platform

Publication date: 2026-07-21

Last updated on: 2026-07-21

Assigner: GitHub, Inc.

Description
PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Versions prior to 0.1.4 have an Insecure Direct Object Reference. The project CRUD endpoints (`GET / PATCH / DELETE /workspaces/{workspace_id}/projects/{project_id}` and `GET .../{project_id}/stats`) gate access on `require_workspace_member(workspace_id)` only, then resolve `project_id` through `ProjectService.get(project_id)` / `update(project_id, ...)` / `delete(project_id)` / `get_stats(project_id)`. None of these calls thread `workspace_id` through to constrain the lookup. A user who is a member of any workspace `W1` can read, modify, delete, or read stats for projects that belong to a different workspace `W2`. PraisonAI Platform version 0.1.4 patches the issue.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-21
Last Modified
2026-07-21
Generated
2026-07-21
AI Q&A
2026-07-21
EPSS Evaluated
N/A
NVD
CVE-2026-47418
EUVD
EUVD-2026-46337

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
mervinpraison praisonai_platform to 0.1.4 (exc)
mervinpraison praisonai_platform 0.1.4
mervinpraison praisonai_platform to 0.1.2 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-47418 is an Insecure Direct Object Reference (IDOR) vulnerability in the PraisonAI platform. It allows authenticated users to access, modify, or delete projects belonging to other workspaces without proper authorization checks. The issue occurs because project endpoints only verify workspace membership but do not validate that the requested project belongs to the specified workspace.

Detection Guidance

To detect this vulnerability, review access logs for the PraisonAI platform endpoints `/workspaces/{workspace_id}/projects/{project_id}` and `/projects/{project_id}/stats`. Look for requests where the `workspace_id` does not match the project's actual workspace. Check for unauthorized access attempts or data exfiltration patterns involving project IDs from different workspaces.

Impact Analysis

An attacker with access to any workspace could manipulate projects across different workspaces by using known or guessable project IDs. This could lead to unauthorized data access, modification, or deletion of sensitive projects, potentially causing data breaches or service disruptions.

Compliance Impact

This vulnerability could lead to unauthorized access or disclosure of sensitive data, violating GDPR's data protection principles or HIPAA's privacy and security rules. Non-compliance may result in legal penalties, reputational damage, and loss of trust.

Mitigation Strategies

Upgrade the PraisonAI platform to version 0.1.4 or later to patch the vulnerability. Ensure all project endpoints validate that the requested project belongs to the specified workspace by including workspace ID constraints in database queries. Review and restrict user permissions to minimize exposure.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-47418. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart