ChurchCRM vulnerable to time-based blind SQL Injection in ConfirmReportEmail.php
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- SQL injection
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-89.
Summary
ChurchCRM is an open-source church management system. A SQL Injection vulnerability exists in the legacy endpoint `/Reports/ConfirmReportEmail.php` in ChurchCRM prior to version 6.5.3. Although the feature was removed from the UI, the file remains deployed and reachable directly via URL. This is a classic case of *dead but reachable code*. Any authenticated user - including one with zero assigned permissions - can exploit SQL injection through the `familyId` parameter. Version 6.5.3 fixes the issue.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- Yes
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA CRM (ChurchCRM) Fixed in 6.5.3
Timeline
- 2026-10-02 Threatist record created from CVE-2025-68400
References
More Churchcrm vulnerabilities
- TI-2026-28325 ChurchCRM Affected by Unauthenticated RCE in Install Wizard CVSS 3.1CRITICAL 10.0
- TI-2025-38761 ChurchCRM has unauthenticated RCE in its Install Wizard CVSS 3.1CRITICAL 10.0
- TI-2024-35802 EventAttendance.php in ChurchCRM 5.7.0 is vulnerable to SQL injection. CVSS 3.1CRITICAL 9.8
- TI-2024-16997 ChurchCRM 5.5.0 /EventEditor.php is vulnerable to Blind SQL Injection (Time-based) via the EventCount POST parameter. CVSS 3.1CRITICAL 9.8
- TI-2025-00963 SQL Injection in ChurchCRM CurrentFundraiser Parameter via BatchWinnerEntry.php CVSS 4.0CRITICAL 9.3
- TI-2025-00962 SQL Injection in ChurchCRM CurrentFundraiser Parameter via DonatedItemEditor.php CVSS 4.0CRITICAL 9.3
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences