SQL Injection in EcclesiaCRM (CVE-2026-35184)
Summary
SQL injection in EcclesiaCRM (CVE-2026-35184). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 8.0.0 or later.
Original description
The description as published by the source.
EcclesiaCRM is CRM Software for church management. Prior to 8.0.0, there is a SQL injection vulnerability in v2/templates/query/queryview.php via the custom and value parameters. This vulnerability is fixed in 8.0.0.
Source: NIST National Vulnerability Database 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-35184 has been found in EcclesiaCRM.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade EcclesiaCRM to 8.0.0 or later.
If unsure, ask your IT team or search "EcclesiaCRM CVE-2026-35184" on the vendor's site.
CVE-2026-35184 (EcclesiaCRM) — CWE-89 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 8.0.0 — apply immediately
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.
SQL injection (CWE-89) exists in EcclesiaCRM.
Check the vendor advisory for the affected versions of EcclesiaCRM.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 8.0.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'EcclesiaCRM' . 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 'EcclesiaCRM' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
EcclesiaCRMを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade EcclesiaCRM to 8.0.0ステージング環境で 8.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- patch github.com
- web gist.github.com