praisonai-platform: Issue endpoints accept any issue_id without workspace ownership check, cross-workspace read/update/delete IDOR
CVE-2026-47415GHSA-xwq8-frcg-77q8
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (praisonai-platform 0.1.4), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI praisonai-platform
- Affected
- < 0.1.4
- Fixed in
- 0.1.4
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-xwq8-frcg-77q8 lists affected ranges: PyPI praisonai-platform >=0 <0.1.4 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-xwq8-frcg-77q8 lists affected ranges: PyPI praisonai-platform >=0 <0.1.4
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 8.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
- EPSS
- CVE-2026-47415: 0.39% estimated exploitation activity in the next 30 days; percentile 33.00 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary Type: Insecure Direct Object Reference. The issue CRUD endpoints (GET / PATCH / DELETE /workspaces/{workspaceid}/issues/{issueid}) gate access on requireworkspacemember(workspaceid) only, then resolve issueid through IssueService.get(issueid) which is a primary-key lookup with no workspace constraint. A user who is a member of any workspace W1 can read, modify, or delete issues that belong to a different workspace W2. File: src/praisonai-platform/praisonaiplatform/services/issueservice.py, lines 72-156; route handlers at src/praisonai-platform/praisonaiplatform/api/routes/issues.py, lines 82-137. Root cause: the route extracts workspaceid from the URL path, uses it solely for the membership gate, then calls IssueService.get(issueid) / IssueService.update(issueid, ...) / IssueService.delete(issueid) without re-checking which workspace the issue actually belongs to. IssueService.get runs a single-key lookup; update and delete call self.get(issueid) first and then mutate the…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-xwq8-frcg-77q8
- Revision 1 · created ·
Published from osv record GHSA-xwq8-frcg-77q8
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-47415 Advisory: praisonai-platform: Issue endpoints accept any issue_id without workspace ownership check, cross-workspace read/update/delete IDOR IDs: CVE-2026-47415, GHSA-xwq8-frcg-77q8 Record: https://patchnext.com/advisories/cve-2026-47415 (revision 2, source checked 26 Oct 2026, 13:41 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: praisonai-platform 0.1.4. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI praisonai-platform: affected < 0.1.4; fixed in 0.1.4 ## Suggested inspection (read-only) - `python -m pip show praisonai-platform`: prints the installed version. Run with the environment that serves production active. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on praisonai-platform. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-xwq8-frcg-77q8 (OSV record GHSA-xwq8-frcg-77q8 lists affected ranges: PyPI praisonai-platform >=0 <0.1.4 (fixed)) - Verified: https://github.com/advisories/GHSA-xwq8-frcg-77q8 (GitHub-reviewed advisory GHSA-xwq8-frcg-77q8 lists affected ranges: PyPI praisonai-platform >=0 <0.1.4) Commands are suggestions: review each one before running it.
Loading voting…