Solidscripting

An issue exists where the system looks up runs using only the `friendlyId` in the 'api.v1.runs.$runParam.replay' endpoint without restricting the search to the caller's runtime environment. This allows an attacker with a valid API key from any tenant who knows a victim's `friendlyId` to replay that run into their own environment and access the victim's task payload.

Certain endpoints fail to enforce proper authorization checks, allowing authenticated attackers with low-privileged accounts to query these endpoints and read financial data beyond their permitted role.

An issue exists where the endpoint "/api/workspaces/{slug}/entity-search/?query type=user mention" returns workspace-member display names, UUIDs, and avatar URLs to any authenticated user who knows the workspace `slug`, regardless of whether the user is a member of that workspace. Additionally, the endpoint exposes ProjectMember rows. This occurs because the `SearchEndpoint` in apps/api/plane/app/views/search/base.py inherits from `BaseAPIView` and only requires authentication without verifying workspace membership.

Insufficient validation of credential references in the inline workflow JSON of nodes that execute inline sub-workflows, such as the Workflow Tool node, allows a shared-workflow editor or any user interacting via the REST API, Public API, or MCP to persist a node referencing a credential they do not own. If the workflow is executed by an identity that possesses the referenced credential, the inline sub-workflow can resolve the secret and transmit it to an external endpoint controlled by an attacker, leading to credential exfiltration.

Three Enterprise Edition endpoints used by the Dynamic Credentials feature fail to perform per-resource ownership or scope checks on target workflows or credentials. This allows an authenticated user, regardless of project membership or credential sharing permissions, to enumerate credential identifiers, names, and types referenced by any private workflow. Additionally, an attacker can initiate an OAuth authorization flow to overwrite another user's stored tokens with tokens from an account they control or revoke those tokens entirely. Consequently, workflows using hijacked credentials execute under the attacker's OAuth identity, potentially leading to data exfiltration to external services and persistent takeover of integrations. This issue specifically affects Enterprise instances with the Dynamic Credentials feature enabled.