CVE-2025-67875: ChurchCRM CRM · Cross-site Scripting
Affects ChurchCRM CRMSource CVE Database V5
Not known to be exploited · CVSS 8.5 High : upgrade to 6.5.3 soon.
Data as of 26 Oct 2026, 15:59 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 9% 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:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/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
- Immediate upgrade of ChurchCRM installations to version 6.5.3 or later, which contains the fix for this vulnerability.
- Review and restrict user permissions to ensure that only trusted users have 'Edit Records' and 'Manage Properties and Classifications' privileges, minimizing the attack surface.
- Implement strict input validation and output encoding on all user-supplied data fields, especially those displayed in administrator profiles, to prevent injection of malicious scripts.
- Conduct regular audits of user roles and access controls to detect and remediate any unauthorized privilege escalations or misconfigurations.
- Monitor logs for unusual profile access or modification activities that could indicate exploitation attempts.
- Educate administrators to be cautious when viewing profile pages and to report any suspicious behavior.
- Employ Content Security Policy (CSP) headers to reduce the impact of potential XSS payloads by restricting the execution of unauthorized scripts.
- Consider implementing multi-factor authentication (MFA) for administrator accounts to mitigate session hijacking risks.
- Regularly back up ChurchCRM data and configurations to enable recovery in case of compromise.
- Stay informed about updates from ChurchCRM and security advisories to promptly address new vulnerabilities.
Description
ChurchCRM is an open-source church management system. A privilege escalation vulnerability exists in ChurchCRM prior to version 6.5.3. An authenticated user with specific mid-level permissions ("Edit Records" and "Manage Properties and Classifications") can inject a persistent Cross-Site Scripting (XSS) payload into an administrator's profile. The payload executes when the administrator views their own profile page, allowing the attacker to hijack the administrator's session, perform administrative actions, and achieve a full account takeover. This vulnerability is a combination of two separate flaws: an Insecure Direct Object Reference (IDOR) that allows any user to view any other user's profile, and a Broken Access Control vulnerability that allows a user with general edit permissions to modify any other user's record properties. Version 6.5.3 fixes the issue.