CVE-2025-62521: ChurchCRM CRM · Code Injection
Affects ChurchCRM CRMSource CVE Database V5
Public exploit available (Metasploit) · CVSS 10.0 Critical : upgrade to 5.21.0 as a priority.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 4.5% chance of exploitation in 30 days – higher than 91% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.21.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
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), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade churchcrm/CRM to 5.21.0.
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 5.21.0 or later to apply the official patch. Until upgrade, restrict access to the setup wizard by network segmentation or firewall rules, allowing only trusted administrators to reach the installation interface. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious input patterns targeting the setup form. Conduct installation in isolated, secure environments to prevent unauthorized access during setup. Monitor logs for unusual activity related to setup routes and configuration file modifications. Educate administrators to verify the integrity of Include/Config.php after installation and before going live. Consider deploying runtime application self-protection (RASP) solutions to detect and prevent code injection attempts. Finally, maintain regular backups of configuration and data to enable recovery in case of compromise.
Description
ChurchCRM is an open-source church management system. Prior to version 5.21.0, a pre-authentication remote code execution vulnerability in ChurchCRM's setup wizard allows unauthenticated attackers to inject arbitrary PHP code during the initial installation process, leading to complete server compromise. The vulnerability exists in `setup/routes/setup.php` where user input from the setup form is directly concatenated into a PHP configuration template without any validation or sanitization. Any parameter in the setup form can be used to inject PHP code that gets written to `Include/Config.php`, which is then executed on every page load. This is more severe than typical authenticated RCE vulnerabilities because it requires no credentials and affects the installation process that administrators must complete. Version 5.21.0 patches the issue.