Skip to main content
VulnerabilityPublished

CVE-2025-68110: ChurchCRM CRM · Information Exposure

Affects ChurchCRM CRMSource CVE Database V5

0

Not known to be exploited · CVSS 10.0 Critical : upgrade to 6.5.3 as a priority.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 36% 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:C/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

  1. Immediately upgrade all ChurchCRM installations to version 6.5.3 or later, where the vulnerability is fixed.
  2. Restrict access to the CRM system and its error messages by implementing network-level controls such as firewalls and VPNs to limit exposure to trusted users only.
  3. Configure the application and web server to suppress detailed error messages in production environments to prevent leakage of sensitive information.
  4. Rotate database credentials used by ChurchCRM after patching to invalidate any potentially exposed secrets.
  5. Implement monitoring and alerting for unusual access patterns or failed login attempts to detect potential exploitation attempts early.
  6. Conduct regular security audits and penetration testing focused on error handling and information disclosure.
  7. Educate administrators and users about the importance of timely patching and secure configuration.
  8. Consider network segmentation to isolate the CRM database from other critical infrastructure to limit lateral movement if credentials are compromised.

Description

ChurchCRM is an open-source church management system. Versions prior to 6.5.3 may disclose database information in an error message including the host, ip, username, and password. Version 6.5.3 fixes the issue.

References

Community reviews

Loading reviews…