Skip to main content
VulnerabilityPublished Updated

CVE-2024-25892: CRM · SQL Injection

Affects CRMSource CVE Database V5

0

Not known to be exploited · CVSS 8.1 High.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Feb 2024

  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

Affected software

ProductAffectedFixed in
GitHubchurchcrm/CRMpkg:github/churchcrm/CRMOther threatsAffected
  • =5.5.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-25892, organizations should first verify if they are running ChurchCRM version 5.5.0 and restrict access to the ConfirmReport.php endpoint, especially the familyId parameter, by implementing web application firewalls (WAF) with custom rules to detect and block SQL injection patterns. Input validation and parameterized queries should be enforced in the application code to sanitize all user inputs rigorously. Until an official patch is released, consider disabling or restricting the vulnerable functionality if feasible. Network-level controls such as IP whitelisting and VPN access can reduce exposure. Regularly monitor application logs for suspicious query patterns or abnormal response times indicative of time-based SQL injection attempts. Additionally, maintain up-to-date backups of the database to enable recovery in case of data tampering or loss. Engage with the ChurchCRM community or vendor for updates and patches and apply them promptly once available.

Description

ChurchCRM 5.5.0 ConfirmReport.php is vulnerable to Blind SQL Injection (Time-based) via the familyId GET parameter.

References

Community reviews

Loading reviews…