Description
PraisonAI Platform (praisonai-platform) before 0.1.9 improperly authorizes deletion of issue dependencies. The DELETE dependency route accepts either endpoint of a dependency edge and checks delete permission only against the caller-selected URL issue. A workspace member who cannot delete a dependency through an owner-created issue endpoint (which returns 403) can delete the same dependency edge by targeting a related member-owned issue endpoint, because permission is validated against the member-owned issue's owner. This allows members to bypass owner/admin authorization and remove owner-created issue dependencies.
Problem types
Product status
Any version before 0.1.9
0.1.9 (semver)
Credits
rexpository
References
github.com/...isonAI/security/advisories/GHSA-mxmx-rh57-jx58
github.com/...isonAI/security/advisories/GHSA-mxmx-rh57-jx58 (GitHub Security Advisory (GHSA-mxmx-rh57-jx58))
github.com/...ommit/846568c7a5d8ce9e71e56e4c213f027c04909753
www.vulncheck.com/...e-authorization-bypass-via-dependencies (VulnCheck Advisory: PraisonAI Platform before 0.1.9 Authorization Bypass via Dependencies)