First published: Tue Feb 18 2025(Updated: )
A vulnerability exists in ChurchCRM 5.13.0 and prior that allows an attacker to execute arbitrary SQL queries by exploiting a time-based blind SQL Injection vulnerability in the EditEventTypes functionality. The newCountName parameter is directly concatenated into an SQL query without proper sanitization, allowing an attacker to manipulate database queries and execute arbitrary commands, potentially leading to data exfiltration, modification, or deletion.
Credit: b7efe717-a805-47cf-8e9a-921fca0ce0ce
Affected Software | Affected Version | How to fix |
---|---|---|
ChurchCRM | <5.13.0 |
To prevent SQL injection, use prepared statements with parameterised queries. Additionally, implement input validation to reject dangerous characters, apply the principle of least privilege to database users to minimise potential damage, and assign appropriate data types in PHP, such as converting newCountName to an integer if it represents a numeric value.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-1023 is classified as a high-severity vulnerability due to its potential for remote code execution through SQL injection.
To fix CVE-2025-1023, update ChurchCRM to version 5.13.1 or later, where the vulnerability has been patched.
CVE-2025-1023 allows attackers to execute arbitrary SQL queries, which could lead to data leakage or manipulation.
Yes, CVE-2025-1023 is easily exploitable due to the lack of proper input sanitization in the affected functionality.
ChurchCRM versions 5.13.0 and prior are affected by CVE-2025-1023.