Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-68275: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in ChurchCRM CRM

0
Critical
VulnerabilityCVE-2025-68275cvecve-2025-68275cwe-79
Published: Wed Dec 17 2025 (12/17/2025, 21:53:22 UTC)
Source: CVE Database V5
Vendor/Project: ChurchCRM
Product: CRM

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.

AI-Powered Analysis

AILast updated: 12/17/2025, 22:15:38 UTC

Technical Analysis

CVE-2025-68275 is a stored cross-site scripting (XSS) vulnerability classified under CWE-79, impacting ChurchCRM, an open-source church management system. Versions prior to 6.5.3 allow malicious actors with authenticated access to inject and store malicious scripts within user-facing pages, specifically the 'View Active People', 'View Inactive People', and 'View All People' pages. When other users visit these pages, the injected scripts execute in their browsers, potentially leading to session hijacking, credential theft, unauthorized actions, or data leakage. The vulnerability is critical, with a CVSS 4.0 score of 9.2, reflecting its high impact on confidentiality and integrity, ease of exploitation (no privileges beyond authentication needed), and the requirement for user interaction. Although no exploits have been reported in the wild, the vulnerability's nature makes it a prime target for attackers aiming to compromise church management systems, which often contain sensitive personal and organizational data. The fix was introduced in version 6.5.3, which properly neutralizes input during web page generation to prevent script injection. The vulnerability's presence in multiple user list views increases the attack surface, making it imperative for administrators to apply patches promptly. Given the authenticated access requirement, attackers would need to compromise or create user accounts, but once inside, the impact can be severe due to the stored nature of the XSS. This vulnerability highlights the importance of secure coding practices in web applications managing sensitive community data.

Potential Impact

For European organizations, particularly churches and religious institutions using ChurchCRM, this vulnerability poses a significant risk to the confidentiality and integrity of personal and organizational data. Exploitation could lead to unauthorized access to user sessions, theft of sensitive information such as personal details of congregation members, and potential manipulation of church records. The stored XSS could also be leveraged to spread malware or conduct phishing attacks within the organization, undermining trust and operational continuity. Given that many European countries have strict data protection regulations (e.g., GDPR), a breach resulting from this vulnerability could lead to regulatory penalties and reputational damage. The requirement for authenticated access limits exposure to some extent, but insider threats or compromised accounts increase risk. The vulnerability could disrupt church operations and erode community trust if exploited. Additionally, the high CVSS score indicates a critical threat level that demands immediate attention to prevent potential widespread impact across European religious organizations using this software.

Mitigation Recommendations

European organizations should immediately upgrade ChurchCRM installations to version 6.5.3 or later to remediate the vulnerability. Beyond patching, administrators should enforce strong authentication controls, including multi-factor authentication (MFA), to reduce the risk of account compromise. Implement strict input validation and output encoding on all user-generated content to prevent injection of malicious scripts. Regularly audit user accounts and permissions to detect and remove unauthorized or dormant accounts. Monitor web application logs for unusual activity indicative of XSS exploitation attempts. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. Conduct security awareness training for users to recognize phishing and social engineering attempts that could lead to account compromise. Consider deploying web application firewalls (WAFs) with rules tailored to detect and block XSS payloads targeting ChurchCRM. Finally, maintain an incident response plan specific to web application attacks to quickly contain and remediate any exploitation.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-12-16T14:17:32.388Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69432992fab815a9fc299edd

Added to database: 12/17/2025, 10:07:14 PM

Last enriched: 12/17/2025, 10:15:38 PM

Last updated: 12/18/2025, 1:28:13 PM

Views: 12

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats