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 newCountName to an integer if it represents a numeric value.
Workaround
No workaround given by the vendor.
Link | Providers |
---|---|
https://github.com/ChurchCRM/CRM/issues/7246 |
![]() ![]() |
Fri, 21 Feb 2025 15: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
|
Tue, 18 Feb 2025 15:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
ssvc
|
Tue, 18 Feb 2025 10:00: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 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. | |
Title | SQL Injection in ChurchCRM newCountName Parameter via EditEventTypes.php | |
Weaknesses | CWE-89 | |
References |
| |
Metrics |
cvssV4_0
|

Status: PUBLISHED
Assigner: Gridware
Published:
Updated: 2025-02-18T14:27:27.899Z
Reserved: 2025-02-04T10:31:51.341Z
Link: CVE-2025-1023

Updated: 2025-02-18T14:27:22.197Z

Status : Analyzed
Published: 2025-02-18T10:15:10.500
Modified: 2025-02-21T15:21:54.417
Link: CVE-2025-1023

No data.

No data.