CVE-2025-67876: ChurchCRM CRM · Cross-site Scripting
Affects ChurchCRM CRMSource CVE Database V5
Not known to be exploited · CVSS 9.3 Critical.
Data as of 25 Oct 2026, 19:02 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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:L/SC:H/SI:H/SA:LExploitation 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 2026-10-25.
What to do
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
Until an official patch is released, European organizations should implement several targeted mitigations: 1) Restrict the 'Manage Groups' permission strictly to trusted users only, minimizing the number of accounts that can inject malicious input. 2) Employ web application firewalls (WAFs) with custom rules to detect and block suspicious JavaScript payloads in HTTP requests related to group role management. 3) Implement server-side input validation and sanitization for group role names, ideally using a whitelist approach to allow only safe characters. 4) Monitor logs and user activity for unusual behavior, such as unexpected changes to group roles or repeated access to affected pages. 5) Educate users, especially administrators, to recognize signs of session hijacking or unusual account activity. 6) Consider isolating ChurchCRM instances from critical networks to limit lateral movement if compromised. 7) Regularly back up data to enable recovery from potential data integrity attacks. 8) Engage with the ChurchCRM community or maintainers to track patch releases and apply updates promptly once available.
Description
ChurchCRM is an open-source church management system. A stored cross-site scripting (XSS) vulnerability exists in ChurchCRM versions 6.4.0 and prior that allows a low-privilege user with the “Manage Groups” permission to inject persistent JavaScript into group role names. The payload is saved in the database and executed whenever any user (including administrators) views a page that displays that role, such as GroupView.php or PersonView.php. This allows full session hijacking and account takeover. As of time of publication, no known patched versions are available.