CVE-2026-39344 ChurchCRM CVE debrief

Who should care

Users of ChurchCRM versions prior to 7.1.0 should be aware of this vulnerability and take steps to mitigate it. This includes upgrading to version 7.1.0 or applying compensating controls to prevent exploitation. Operators, administrators, and security teams responsible for ChurchCRM deployments should prioritize assessment and remediation.

Technical summary

The vulnerability is caused by the lack of sanitization or encoding of the username parameter received from the URL on the login page of ChurchCRM, an open-source church management system. This allows attackers to insert malicious JavaScript scripts, which can be executed on the client side if successful. The vulnerability has a CVSS score of 8.1 and is classified as HIGH severity. Affected users should be aware of the potential for sensitive data theft or display replacement via XSS.

Defensive priority

High

Recommended defensive actions

• Upgrade ChurchCRM to version 7.1.0 or later
• Implement input validation and sanitization for the username parameter
• Use a web application firewall (WAF) to detect and prevent XSS attacks
• Monitor for suspicious activity on the login page
• Educate users on the risks of XSS attacks and the importance of secure login practices
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The vulnerability is documented in the CVE record and the NVD detail page. The fix is available in ChurchCRM version 7.1.0. Users should verify their version and apply the fix or compensating controls as needed. Evidence is limited to public sources and may not reflect all affected deployments or variations.

Official resources