Leantime versions 3.6.2 and earlier have an authorization bypass vulnerability (CWE-639) that allows authenticated users to access milestone data from projects they are not assigned to. By supplying arbitrary integer milestone IDs to the tickets.getMilestone JSON-RPC endpoint, attackers can enumerate and read milestone titles, descriptions, and timelines across all projects on the instance regardless of membership.
The Kirki – Freeform Page Builder, Website Builder & Customizer WordPress plugin contains an authorization bypass vulnerability (CWE-639) in all versions up to and including 6.0.14. This flaw allows unauthenticated attackers to read the full title, content, and excerpt of any WordPress post, including drafts, pending, private, password-protected, and trashed posts, by manipulating the 'context' parameter with an arbitrary post ID. The vulnerability arises from missing validation on a user-controlled key.
Shopper is a Headless e-commerce Admin Panel. Prior to 2.8.0, three related defects on admin Livewire components allowed data tampering, sensitive data disclosure, and stored XSS. First, several Livewire components in the admin panel exposed Eloquent model identifiers as public properties without the `#[Locked]` attribute. An authenticated user could rewrite the wire payload from the browser to target any record id, bypassing the implicit scoping enforced by the page routing. Second, `Customers/Create::store()` re-passed a `Hidden` `_password` form field straight into the create payload. The plaintext password was rendered into the HTML and transported through the Livewire snapshot in clear text, exposing credentials in the page DOM and in any logging that captures Livewire payloads. Finally, the product barcode field was rendered through `DNS1DFacade::getBarcodeHTML()` with `{!! !!}`. An attacker with `edit_products` permission could persist malicious payload in the barcode field that would execute in the browser of any admin user viewing that product, enabling session theft and privileged-action chaining. Starting in v2.8.0, all vulnerable Livewire model identifiers are now marked `#[Locked]`; `Customers/Create` no longer round-trips the password through a Hidden form field; the plaintext password is hashed at action boundary and never returned to the client; and the product barcode rendering now escapes the value before passing it to the barcode generator and the output is wrapped in an `<svg>` context that does not interpret event handlers. No known workarounds are available.
ITFlow provides an IT documentation, ticketing and accounting system for small managed service providers. Prior to version 26.05, low-privileged authenticated agent can retrieve plaintext credentials and TOTP secrets belonging to another client by directly requesting the credential edit modal with an arbitrary `credential_id`. The endpoint does not enforce client scoping or object-level authorization before loading and decrypting the credential record. Version 26.05 fixes the issue.
Cal.com OSS ships lacks authorization on webhook teamId creation, allowing any authenticated user to create a webhook on any team via unvalidated teamId injection, then steal booking data, including fields like organizer/attendee emails and custom responses, and conditionally video-call passwords, by triggering webhook delivery.
IBM Sterling B2B Integrator and IBM Sterling File Gateway versions 6.2.0.0 through 6.2.0.5_2, 6.2.1.0 through 6.2.1.1_2, and 6.2.2.0 through 6.2.2.0_1 contain a vulnerability that allows an unauthenticated user to bypass authentication and read sensitive information via a specially crafted HTTP request. This issue is classified as an authorization bypass due to user-controlled key manipulation (CWE-639). The vulnerability has a medium severity with a CVSS score of 5.3. No official patch or remediation guidance has been provided yet.
Authorization bypass through User-Controlled key vulnerability in Universe Software Computer Marketing Trade and Industry Inc. Online Registration and Workflow Management System allows Exploiting Trust in Client.
This issue affects Online Registration and Workflow Management System: through 12022026.
Authorization Bypass Through User-Controlled Key (CWE-639) in Kibana can lead to information disclosure via user-supplied identifiers that reference scheduled query result data from Kibana Spaces the requester is not authorized to access.
CVE-2026-56147 is an authorization bypass vulnerability in Elastic Kibana that allows low-privileged authenticated users to access, modify, or delete case attachments belonging to feature areas they are not authorized to access. This occurs due to inconsistent file access authorization logic, where access control checks and resource retrieval use different resolution mechanisms. The vulnerability can lead to unauthorized information disclosure and compromise of case attachment integrity.
PraisonAI Platform versions prior to 0.1.4 contain an authorization bypass vulnerability due to insecure direct object references in agent CRUD endpoints. Users who are members of any workspace can access agents belonging to other workspaces by manipulating agent IDs without proper workspace validation. This allows unauthorized reading, modification, or deletion of agents across workspaces. Version 0.1.4 addresses this issue.
CVE-2026-47418 is an authorization bypass vulnerability in the PraisonAI Platform prior to version 0.1.4. The platform's project-related endpoints check only workspace membership but do not properly constrain project access by workspace, allowing users to access projects in other workspaces. This insecure direct object reference (IDOR) flaw permits unauthorized reading, modification, deletion, or statistics viewing of projects outside a user's workspace.
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.
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 issue CRUD endpoints (`GET / PATCH / DELETE /workspaces/{workspace_id}/issues/{issue_id}`) gate access on `require_workspace_member(workspace_id)` only, then resolve `issue_id` through `IssueService.get(issue_id)` 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`. PraisonAI Platform version 0.1.4 patches the issue.
CVE-2026-47414 is an authorization bypass vulnerability in the PraisonAI Platform prior to version 0.1.4. The issue arises because five label-related API endpoints only verify workspace membership but do not confirm that the label_id or issue_id parameters belong to the specified workspace. This allows unauthorized access to labels and issues across workspaces. The vulnerability is fixed in version 0.1.4.
PraisonAI Platform versions prior to 0.1.4 contain an authorization bypass vulnerability (CWE-639) in the activity log endpoint. The GET /workspaces/{workspace_id}/issues/{issue_id}/activity endpoint allows any user who is a member of any workspace to access the full activity log of issues across all workspaces, due to missing workspace constraints in the database query. This issue is fixed in version 0.1.4.
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.