n8n contact exposure and unintended writes via OData filter injection
n8n-io n8n
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
n8n-io n8n
| Product | Affected | Fixed in |
|---|---|---|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
n8n before 1.123.85, 2.x before 2.43.5, and 2.44.x before 2.44.1 contains an OData $filter injection vulnerability in the Microsoft Outlook contact lookup and Microsoft SharePoint v1 item update nodes, which build $filter string literals from expression-bindable parameters without escaping. Attackers who supply untrusted input to such workflows can inject single quotes to dump the bound mailbox's entire contact list or redirect SharePoint writes onto unintended list items within the stored credential's scope.
From the CVE record · VulnCheck
The Microsoft Outlook contact lookup and Microsoft SharePoint v1 item update nodes in n8n do not escape expression-bindable values used in OData $filter strings. An attacker who can supply untrusted input to a workflow can inject single quotes to dump the bound mailbox’s contact list or redirect SharePoint writes to unintended list items within the stored credential’s scope.
Teams running n8n before 1.123.85, 2.x before 2.43.5, or 2.44.x before 2.44.1 should check their deployments.