Weblover12

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.

Langflow is a tool for building and deploying AI-powered agents and workflows. In the CSV Agent node, the variable `allow dangerous code` is hardcoded to `True`, which automatically exposes LangChain's Python REPL tool (`python repl ast`). This allows an attacker to execute arbitrary Python and operating system commands on the server through prompt injection, leading to full Remote Code Execution (RCE). Additionally, some reports indicate a deserialization flaw in the flow import endpoint where malicious YAML payloads can be used to execute arbitrary code without authentication. Over 3,000 instances have been identified globally.

n8n is a workflow automation platform. A Cross-Site Scripting (XSS) issue exists in the handling of webhook responses and related HTTP endpoints. The Content Security Policy (CSP) sandbox protection may not be applied correctly under certain conditions. An authenticated user with appropriate permissions could exploit this to execute malicious scripts with same-origin privileges when other users interact with a crafted workflow, potentially leading to session hijacking and account takeover.

n8n is a workflow automation platform. A flaw in the HTTP Request node’s credential domain validation could allow an authenticated attacker to send requests with credentials to unintended domains, potentially resulting in credential exfiltration. This issue specifically impacts users who have credentials with wildcard domain patterns (e.g., `*.example.com`) configured in the "Allowed domains" setting. The vulnerable component is the HTTP Request node. The vulnerable setting is the "Allowed domains" setting.