Metrics
Affected Vendors & Products
Solution
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 CurrentFundraiser to an integer if it represents a numeric value.
Workaround
No workaround given by the vendor.
Link | Providers |
---|---|
https://github.com/ChurchCRM/CRM/issues/7254 |
![]() ![]() |
Tue, 25 Feb 2025 21:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
First Time appeared |
Churchcrm
Churchcrm churchcrm |
|
CPEs | cpe:2.3:a:churchcrm:churchcrm:*:*:*:*:*:*:*:* | |
Vendors & Products |
Churchcrm
Churchcrm churchcrm |
|
Metrics |
cvssV3_1
|
Wed, 19 Feb 2025 15:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
ssvc
|
Wed, 19 Feb 2025 09:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | A vulnerability exists in ChurchCRM 5.13.0. and prior that allows an attacker to execute arbitrary SQL queries by exploiting a boolean-based and time-based blind SQL Injection vulnerability in the BatchWinnerEntry functionality. The CurrentFundraiser parameter is directly concatenated into an SQL query without sufficient sanitization, allowing an attacker to manipulate database queries and execute arbitrary commands, potentially leading to data exfiltration, modification, or deletion. Please note the vulnerability requires Administrator privileges. | |
Title | SQL Injection in ChurchCRM CurrentFundraiser Parameter via BatchWinnerEntry.php | |
Weaknesses | CWE-89 | |
References |
| |
Metrics |
cvssV4_0
|

Status: PUBLISHED
Assigner: Gridware
Published:
Updated: 2025-02-19T14:55:42.227Z
Reserved: 2025-02-08T04:11:56.925Z
Link: CVE-2025-1135

Updated: 2025-02-19T14:55:37.009Z

Status : Analyzed
Published: 2025-02-19T09:15:10.823
Modified: 2025-02-25T21:18:49.493
Link: CVE-2025-1135

No data.

No data.