dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-47417

HIGH · 8.1 CVSS v3.1 Published 2026-07-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click 4 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 comment endpoints (`POST /workspaces/{workspace_id}/issues/{issue_id}/comments` and `GET .../comments`) gate access on `require_workspace_member(workspace_id)` only, then call `CommentService.create(issue_id=issue_id, ...)` and `CommentService.list_for_issue(issue_id)` without verifying that `issue_id` belongs to `workspace_id`. A user who is a member of any workspace `W1` can read every comment on, and post new comments to, any issue in any other workspace `W2`. PraisonAI Platform version 0.1.4 patches the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

PraisonAI Platform versions before 0.1.4 contain an IDOR vulnerability in the comment endpoints. The POST and GET comment endpoints only verify user membership in workspace_id but fail to validate that the issue_id actually belongs to that workspace, allowing any workspace member to access comments on issues in any other workspace.

MitigationUpgrade to PraisonAI Platform version 0.1.4, which includes a patch that validates issue ownership within the workspace before allowing comment access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed PraisonAI Platform version
    Run 'pip show praisonai' or check the package version in your Python environment, or look for version metadata in the deployed application
    Affected if Version is lower than 0.1.4
  2. Identify comment endpoint exposure
    Review API routes or application configuration to locate the comment GET and POST endpoints (typically /workspaces/{workspace_id}/issues/{issue_id}/comments or similar path patterns)
    Affected if Comment endpoints exist and accept workspace_id and issue_id parameters
  3. Verify authorization logic for issue_id validation
    Inspect the source code of the comment endpoint handlers to determine if they check that the issue_id belongs to the workspace_id provided in the request
    Affected if Code only validates workspace membership but does not verify that the issue_id is associated with that specific workspace_id
  4. Test cross-workspace comment access
    As a member of one workspace, attempt to access or modify comments on an issue belonging to a different workspace by manipulating the issue_id parameter while using a valid workspace_id you have access to
    Affected if Requests succeed and return or modify comments from issues outside your workspace

A user is affected if running PraisonAI Platform version prior to 0.1.4 AND the comment endpoints are exposed, since the missing issue_id-to-workspace validation allows unauthorized cross-workspace comment access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to PraisonAI Platform version 0.1.4, which includes a patch that validates issue ownership within the workspace before allowing comment access.

Recommended fix High confidence

0.1.4

  1. Check current installed version of PraisonAI Platform
  2. Upgrade PraisonAI Platform to version 0.1.4 or later using the package manager or dependency management tool used in your deployment (e.g., pip install --upgrade praisonai or equivalent)
  3. Verify the upgrade completed successfully and the new version is 0.1.4 or higher
  4. Test that the comment endpoints now properly verify that issue_id belongs to workspace_id before allowing access

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA3.0 h
13.0 hours of engineering $2,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47417 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47417 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data