CVE-2025-68275: ChurchCRM CRM · Cross-site Scripting
Affects ChurchCRM CRMSource CVE Database V5
Not known to be exploited · CVSS 9.2 Critical : upgrade to 6.5.3 as a priority.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.5.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:A/VC:H/VI:H/VA:N/SC:H/SI:H/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Dec 2025
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
Upgrade churchcrm/CRM to 6.5.3.
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
1. Immediately upgrade ChurchCRM installations to version 6.5.3 or later, which contains the fix for this vulnerability. 2. Implement strict input validation and output encoding on all user-supplied data, especially on pages displaying user information. 3. Deploy a Web Application Firewall (WAF) with rules to detect and block XSS payloads targeting the affected endpoints. 4. Conduct regular security audits and code reviews focusing on input handling and sanitization. 5. Educate users and administrators about phishing and social engineering risks, as exploitation requires user interaction. 6. Monitor application logs and user activity for unusual behavior indicative of XSS exploitation attempts. 7. Restrict administrative privileges to minimize the risk of malicious input injection. 8. Consider implementing Content Security Policy (CSP) headers to reduce the impact of potential XSS attacks. 9. Backup CRM data regularly to enable recovery in case of compromise. 10. Engage with the ChurchCRM community for updates and security advisories.
Description
ChurchCRM is an open-source church management system. Versions prior to 6.5.3 have a stored cross-site scripting vulnerability on the pages `View Active People`, `View Inactive people`, and `View All People`. Version 6.5.3 fixes the issue.