ChurchCRM has Stored Cross-Site Scripting (XSS) in Create Events in Church Calendar, Leading to Account Takeover
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- Passive
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Cross-site scripting
- Confidentiality · integrity · availability
- None · High · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-79.
Summary
ChurchCRM is an open-source church management system. Versions prior to 6.7.2 have a Stored Cross-Site Scripting (XSS) vulnerability occurs in Create Events in Church Calendar. Users with low privileges can create XSS payloads in the Description field. This payload is stored in the database, and when other users view that event (including the admin), the payload is triggered, leading to account takeover. Version 6.7.2 fixes the vulnerability.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA CRM (ChurchCRM) Fixed in 6.7.2
Timeline
- 2026-10-02 Threatist record created from CVE-2026-24855
References
More Churchcrm vulnerabilities
- TI-2026-28325 ChurchCRM Affected by Unauthenticated RCE in Install Wizard CVSS 3.1CRITICAL 10.0
- TI-2025-38761 ChurchCRM has unauthenticated RCE in its Install Wizard CVSS 3.1CRITICAL 10.0
- TI-2024-35802 EventAttendance.php in ChurchCRM 5.7.0 is vulnerable to SQL injection. CVSS 3.1CRITICAL 9.8
- TI-2024-16997 ChurchCRM 5.5.0 /EventEditor.php is vulnerable to Blind SQL Injection (Time-based) via the EventCount POST parameter. CVSS 3.1CRITICAL 9.8
- TI-2025-41969 ChurchCRM vulnerable to time-based blind SQL Injection in ConfirmReportEmail.php CVSS 4.0CRITICAL 9.3
- TI-2025-00963 SQL Injection in ChurchCRM CurrentFundraiser Parameter via BatchWinnerEntry.php CVSS 4.0CRITICAL 9.3
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences