ChurchCRM
SQL Injection in ChurchCRM newCountName Parameter via EditEventTypes.php
A vulnerability exists in ChurchCRM 5.13.0 and prior that allows an attacker to execute arbitrary SQL queries by exploiting a time-based blind SQL Injection vulnerability in the EditEventTypes functionality. The newCountName parameter is directly concatenated into an SQL query without proper sanitization, allowing an attacker to manipulate database queries and execute arbitrary commands, potentially leading to data exfiltration, modification, or deletion.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- ChurchCRM 5.13.0 and prior
Mitigation
To prevent SQL injection, use prepared statements with parameterised queries. Additionally, implement input validation to reject dangerous characters, apply the principle of least privilege to database users to minimise potential damage, and assign appropriate data types in PHP, such as converting newCountName to an integer if it represents a numeric value.
Timeline
Days relative to CVE publicationFirst public PoC 258 days after publication; not in CISA KEV. First PoC: nuclei template: ChurchCRM - SQL Injection (nuclei template, 3 Nov 2025).
PoC repositories
Found on GitHub.No PoC repositories found yet.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| nuclei template | nuclei template: ChurchCRM - SQL Injection | 3 Nov 2025 | 14 Nov 2026 |