CVE-2024-25894: ChurchCRM · SQL Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Feb 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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
AI-suggested
- Immediately restrict external access to the EventEditor.php endpoint, ideally limiting it to trusted internal networks or VPN users.
- Deploy a Web Application Firewall (WAF) with rules specifically targeting SQL injection patterns, including time-based blind SQLi detection.
- Conduct thorough input validation and sanitization on all POST parameters, especially EventCount, to prevent injection attacks.
- Monitor application logs and database query patterns for anomalies indicative of SQL injection attempts, such as unusual delays or malformed queries.
- If possible, downgrade or temporarily disable the vulnerable functionality until a patch is released.
- Engage with the ChurchCRM development community or vendor to obtain or contribute to a security patch addressing this vulnerability.
- Educate administrators and users about the risk and signs of exploitation to enable rapid detection and response.
- Regularly back up the database and verify backup integrity to enable recovery in case of data corruption or loss.
- Consider deploying database activity monitoring tools to detect and alert on suspicious SQL commands.
- Plan for rapid patch deployment once an official fix becomes available.
Description
ChurchCRM 5.5.0 /EventEditor.php is vulnerable to Blind SQL Injection (Time-based) via the EventCount POST parameter.