34Selen

The GraphQL node fails to enforce the Allowed HTTP Request Domains restriction on HTTP-based credentials, including Header Auth, Basic Auth, Query Auth, and OAuth. This differs from the behavior of the HTTP Request node. An authenticated user with permissions to create or edit workflows can redirect the node endpoint to a server under their control to exfiltrate restricted credentials. This issue specifically affects instances where a credential has Allowed HTTP Request Domains configured and is accessible to users who are not the owners of that credential.

An authorization bypass exists in the Evaluations feature within the 'POST /workflows/{workflowId}/test-runs/new' endpoint. The system incorrectly authorizes access using the `workflow:read` scope instead of the required `workflow:execute` scope. This broken access control allows an authenticated user with read-only RBAC (Role-Based Access Control) project roles to trigger a real evaluation test run. Such an action causes the workflow to execute via the internal workflow runner, potentially leading to unauthorized outbound API calls, data mutations, or other side effects in connected downstream systems.

An authenticated user with permissions to create or modify workflows and access to a SecurityScorecard credential with limited allowed domains can configure the SecurityScorecard node's report download operation to target an attacker-controlled URL. The node attaches the SecurityScorecard API token to the outbound request, which allows the credential to be sent to an external host, bypassing configured limitations and resulting in credential exfiltration.

An Access Control List (ACL) permission bypass exists in team folders. A user granted READ and CREATE permissions, but lacking UPDATE permissions, can unauthorizedly rename files within the team folder.

A stored Cross-Site Scripting (XSS) issue exists in the Projects component. When administrative detail views for campaigns, emails, or forms display project tags and popovers, user-supplied project names are rendered without proper sanitization. An authenticated user with permissions to create or edit projects can inject malicious script payloads. When an administrator hovers over a tag associated with a compromised project, the script executes in their browser session, potentially allowing the attacker to perform administrative actions, change system configurations, or exfiltrate sensitive data.

The '/chat' WebSocket endpoint used by the Chat Trigger node's Hosted Chat feature fails to verify if an incoming connection is authorized to interact with the target execution. An unauthenticated remote attacker who identifies a valid execution ID for a workflow in a waiting state can attach to that execution, receive the pending prompt intended for the legitimate user, and submit arbitrary input to resume or influence downstream workflow behavior.

n8n is a workflow automation platform. When Lightweight Directory Access Protocol (LDAP) authentication is enabled, n8n automatically links an LDAP identity to an existing local account if the LDAP email attribute matches the local account's email. An authenticated LDAP user who can control their LDAP email attribute can set it to match another user's email, including an administrator's, and gain full access to that account upon login. The account linkage persists even if the LDAP email is reverted, resulting in a permanent account takeover. LDAP authentication must be configured and active for this to occur.

Discourse is an open source discussion platform. Trust Level 4 (TL4) users could publish topics into staff-only categories using the `publish to category` topic timer, bypassing intended authorization controls.

An authorization flaw exists in Apache Airflow that could allow an authenticated user with limited task permissions to view task logs without proper authorization. The issue affects systems where users have custom permissions restricting access to task logs, but still permit task access.