Vulnerability in Erupt (CVE-2026-111390)
Summary
Vulnerability in Erupt (CVE-2026-111390). Confidential information can be exposed externally. Exploitable via POST /erupt-api/data/table/{erupt}..
Original description
The description as published by the source.
Erupt through 2.3.0 contains an HQL injection vulnerability that allows authenticated users to bypass tree-scoped data filters by injecting unescaped quotes into the linkTreeVal parameter of POST /erupt-api/data/table/{erupt}. Attackers holding query permission on entities with String-keyed linkTree targets can append always-true OR clauses or boolean subqueries to read data from other mapped entities.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-111390 has been found in Erupt.
Attackers can target a specific entry point like POST /erupt-api/data/table/{erupt}. over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Erupt CVE-2026-111390" on the vendor's site.
CVE-2026-111390 (Erupt) — CWE-564 / CVSS v3 5.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /erupt-api/data/table/{erupt}.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-564) exists in Erupt. Attackers reach the vulnerable code path via POST /erupt-api/data/table/{erupt}..
Check the vendor advisory for the affected versions of Erupt. Attack surface: POST /erupt-api/data/table/{erupt}..
Severity: Medium (CVSS 5.3/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /erupt-api/data/table/{erupt}. requests with malformed payloads or SQL meta-characters. Run grep -r 'Erupt' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Erupt' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Eruptを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /erupt-api/data/table/{erupt}.' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /erupt-api/data/table/{erupt}.への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /erupt-api/data/table/{erupt}. on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。