GHSA-mp4j-h6gh-f6mp
MEDIUMGHSA-mp4j-h6gh-f6mp is a medium-severity (CVSS 6.8) vulnerability in n8n. O3 Security confirms whether GHSA-mp4j-h6gh-f6mp is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
n8n has SQL Injection in SeaTable Node
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
n8nnpmDescription
Impact
A flaw in the SeaTable node's row:search and row:get operations allowed user-controlled input to be concatenated directly into SQL query strings without escaping or parameterization. In workflows where external user input is passed via expressions into the SeaTable node's search or row retrieval parameters, an attacker could manipulate the constructed query to retrieve unintended rows from the connected SeaTable base, bypassing row-level filtering logic implemented in the workflow.
Exploitation requires a specific workflow configuration:
- The SeaTable node must be used with user-controlled input passed via expressions (e.g., from a form or webhook) into the
searchTermorrowIdparameters.
Patches
The issue has been fixed in n8n versions 1.123.32, 2.17.4, and 2.18.1. Users should upgrade to one of these versions or later to remediate the vulnerability.
Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Limit workflow creation and editing permissions to fully trusted users only.
- Disable the SeaTable node by adding
n8n-nodes-base.seaTableto theNODES_EXCLUDEenvironment variable. - Avoid passing unvalidated external user input into SeaTable node search or row retrieval parameters via expressions.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | n8n | all versions | 1.123.32 |
| 📦npm | n8n | ≥ 2.18.0&&< 2.18.1 | 2.18.1 |
| 📦npm | n8n | ≥ 2.0.0&&< 2.17.4 | 2.17.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for n8n. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update n8n to 1.123.32 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mp4j-h6gh-f6mp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-mp4j-h6gh-f6mp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-mp4j-h6gh-f6mp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-mp4j-h6gh-f6mp in your dependencies?
O3 detects GHSA-mp4j-h6gh-f6mp across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.