CVE-2025-67877: ChurchCRM CRM · SQL Injection
Affects ChurchCRM CRMSource CVE Database V5
Public exploit available · CVSS 7.4 High : upgrade to 6.5.3 as a priority.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.5.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 17 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade churchcrm/CRM to 6.5.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubchurchcrm/CRMpkg:github/churchcrm/CRMOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should immediately upgrade ChurchCRM installations to version 6.5.3 or later, where the vulnerability is patched. Until the upgrade is applied, organizations should implement strict input validation and sanitization on the PersonAddress parameter at the web application firewall (WAF) or reverse proxy level to block SQL injection payloads. Employing parameterized queries or prepared statements in custom integrations can further reduce risk. Monitoring database logs for unusual queries and setting up alerts for suspicious activity related to the CartToFamily.php endpoint is recommended. Additionally, enforcing strong authentication controls and limiting user privileges can reduce the attack surface. Regular security audits and penetration testing focused on input validation in ChurchCRM deployments will help detect similar issues proactively.
Description
ChurchCRM is an open-source church management system. Versions prior to 6.5.3 have a SQL injection vulnerability in the `src/CartToFamily.php` file, specifically in how the `PersonAddress` POST parameter is handled. Unlike other parameters in the same file which are correctly cast to integers using the `InputUtils` class, the `PersonAddress` parameter is missing the type definition. This allows an attacker to inject arbitrary SQL commands directly into the query. Version 6.5.3 fixes the issue.