Skip to main content
VulnerabilityPublished

CVE-2025-66395: ChurchCRM CRM · SQL Injection

Affects ChurchCRM CRMSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High : upgrade to 6.5.3 soon.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
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:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 6.5.3.

Affected software

ProductAffectedFixed in
GitHubchurchcrm/CRMpkg:github/churchcrm/CRMOther threatsAffected
  • <6.5.3
Fixed in
  • 6.5.3

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 upgrades are applied, implement strict access controls to limit authenticated user accounts and monitor for unusual database queries or application behavior indicative of SQL injection attempts. Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection payloads targeting the WhichType parameter. Conduct regular code reviews and penetration testing focused on input validation and sanitization. Additionally, enforce the principle of least privilege for user accounts within ChurchCRM to reduce the risk posed by compromised credentials. Maintain comprehensive logging and alerting on database queries to detect exploitation attempts early. Finally, ensure backups are current and tested to enable recovery from data corruption or deletion.

Description

ChurchCRM is an open-source church management system. Prior to version 6.5.3, a SQL injection vulnerability exists in the `src/ListEvents.php` file. When filtering events by type, the `WhichType` POST parameter is not properly sanitized or type-casted before being used in multiple SQL queries. This allows any authenticated user to execute arbitrary SQL commands, including time-based blind SQL injection attacks. Any authenticated user, regardless of their privilege level, can execute arbitrary queries on the database. This could allow them to exfiltrate, modify, or delete any data in the database, including user credentials, financial data, and personal information, leading to a full compromise of the application's data. Version 6.5.3 fixes the issue.

References

Community reviews

Loading reviews…