CVE-2025-68111 identifies a SQL injection vulnerability in the open-source ChurchCRM software, specifically in versions before 6.5.3. The flaw exists in the eGive.php file within the 'ReImport' feature, where the application fails to properly sanitize the 'MissingEgive_FamID_...' POST parameter. An attacker with authenticated access and finance privileges can exploit this by injecting malicious SQL commands, which the backend database executes. This improper neutralization of special elements used in SQL commands (CWE-89) allows the attacker to perform unauthorized operations such as reading sensitive financial and personal data, modifying records, or deleting critical information. The vulnerability does not require user interaction beyond the crafted request but does require elevated privileges, limiting exploitation to trusted users or compromised accounts. The CVSS v3.1 score is 7.2 (high), reflecting network exploitability with low attack complexity but requiring high privileges. No known exploits are currently reported in the wild. The vendor has addressed the issue in version 6.5.3 by implementing proper input validation and parameterized queries to prevent injection attacks.

For European organizations using ChurchCRM, especially churches and community groups managing sensitive donor and member financial data, this vulnerability poses a significant risk. Exploitation could lead to unauthorized disclosure of personal and financial information, violating data protection regulations such as GDPR. Data integrity could be compromised by unauthorized modifications or deletions, disrupting financial reporting and operational continuity. The requirement for finance-level privileges means insider threats or compromised accounts are primary vectors, but the impact remains severe due to the sensitivity of the data involved. Organizations could face reputational damage, regulatory penalties, and operational disruptions if exploited. Given the open-source nature of ChurchCRM and its adoption in smaller organizations, some may lack robust security controls, increasing risk exposure.

Organizations should immediately upgrade ChurchCRM installations to version 6.5.3 or later, where the vulnerability is patched. In addition, implement strict access controls and monitoring on finance-privileged accounts to detect and prevent unauthorized use. Employ web application firewalls (WAFs) with custom rules to detect anomalous SQL injection patterns targeting the 'ReImport' functionality. Conduct regular audits of database logs for suspicious queries or modifications. Enforce multi-factor authentication (MFA) for users with elevated privileges to reduce the risk of account compromise. Educate finance users on secure handling of credentials and suspicious activity reporting. For organizations unable to upgrade immediately, consider disabling or restricting access to the 'ReImport' feature as a temporary mitigation. Finally, maintain regular backups of CRM data to enable recovery in case of data tampering or loss.