SQL Injection in ChurchCRM (CVE-2026-39341)
Summary
SQL injection in ChurchCRM (CVE-2026-39341). Confidential information can be exposed externally. Mitigation: upgrade to 7.1.0 or later.
Original description
The description as published by the source.
ChurchCRM is an open-source church management system. Prior to 7.1.0, the application is vulnerable to time-based SQL injection due to an improper input validation. Endpoint Reports/ConfirmReportEmail.php?familyId= is not correctly sanitising user input, specifically, the sanitised input is not used to create the SQL query. This vulnerability is fixed in 7.1.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-39341 has been found in ChurchCRM.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade ChurchCRM to 7.1.0 or later.
If unsure, ask your IT team or search "ChurchCRM CVE-2026-39341" on the vendor's site.
CVE-2026-39341 (ChurchCRM) — CWE-89 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Patched: 7.1.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 ChurchCRM.
Check the vendor advisory for the affected versions of ChurchCRM.
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.
Update to 7.1.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 'ChurchCRM' . 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 'ChurchCRM' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
ChurchCRMを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade ChurchCRM to 7.1.0ステージング環境で 7.1.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