Filtered by vendor Churchcrm
Subscribe
Total
55 CVE
CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
---|---|---|---|---|---|
CVE-2022-36137 | 1 Churchcrm | 1 Churchcrm | 2025-04-25 | N/A | 4.8 MEDIUM |
ChurchCRM Version 4.4.5 has XSS vulnerabilities that allow attackers to store XSS via location input sHeader. | |||||
CVE-2022-36136 | 1 Churchcrm | 1 Churchcrm | 2025-04-25 | N/A | 4.8 MEDIUM |
ChurchCRM Version 4.4.5 has XSS vulnerabilities that allow attackers to store XSS via location input Deposit Comment. | |||||
CVE-2024-25898 | 1 Churchcrm | 1 Churchcrm | 2025-03-28 | N/A | 6.1 MEDIUM |
A XSS vulnerability was found in the ChurchCRM v.5.5.0 functionality, edit your event, where malicious JS or HTML code can be inserted in the Event Sermon field in EventEditor.php. | |||||
CVE-2024-53438 | 1 Churchcrm | 1 Churchcrm | 2025-03-28 | N/A | 9.8 CRITICAL |
EventAttendance.php in ChurchCRM 5.7.0 is vulnerable to SQL injection. An attacker can exploit this vulnerability by manipulating the 'Event' parameter, which is directly interpolated into the SQL query without proper sanitization or validation, allowing attackers to execute arbitrary SQL commands. | |||||
CVE-2023-24690 | 1 Churchcrm | 1 Churchcrm | 2025-03-24 | N/A | 5.4 MEDIUM |
ChurchCRM 4.5.3 and below was discovered to contain a stored cross-site scripting (XSS) vulnerability at /api/public/register/family. | |||||
CVE-2023-24686 | 1 Churchcrm | 1 Churchcrm | 2025-03-24 | N/A | 4.8 MEDIUM |
An issue in the CSV Import function of ChurchCRM v4.5.3 and below allows attackers to execute arbitrary code via importing a crafted CSV file. | |||||
CVE-2023-24685 | 1 Churchcrm | 1 Churchcrm | 2025-03-24 | N/A | 7.2 HIGH |
ChurchCRM v4.5.3 and below was discovered to contain a SQL injection vulnerability via the Event parameter under the Event Attendance reports module. | |||||
CVE-2023-24684 | 1 Churchcrm | 1 Churchcrm | 2025-03-24 | N/A | 7.2 HIGH |
ChurchCRM v4.5.3 and below was discovered to contain a SQL injection vulnerability via the EID parameter at GetText.php. | |||||
CVE-2024-25897 | 1 Churchcrm | 1 Churchcrm | 2025-03-17 | N/A | 9.8 CRITICAL |
ChurchCRM 5.5.0 FRCatalog.php is vulnerable to Blind SQL Injection (Time-based) via the CurrentFundraiser GET parameter. | |||||
CVE-2024-25896 | 1 Churchcrm | 1 Churchcrm | 2025-03-17 | N/A | 5.3 MEDIUM |
ChurchCRM 5.5.0 EventEditor.php is vulnerable to Blind SQL Injection (Time-based) via the EID POST parameter. | |||||
CVE-2024-25895 | 1 Churchcrm | 1 Churchcrm | 2025-03-17 | N/A | 6.1 MEDIUM |
A reflected cross-site scripting (XSS) vulnerability in ChurchCRM 5.5.0 allows remote attackers to inject arbitrary web script or HTML via the type parameter of /EventAttendance.php | |||||
CVE-2024-25894 | 1 Churchcrm | 1 Churchcrm | 2025-03-17 | N/A | 9.8 CRITICAL |
ChurchCRM 5.5.0 /EventEditor.php is vulnerable to Blind SQL Injection (Time-based) via the EventCount POST parameter. | |||||
CVE-2024-25893 | 1 Churchcrm | 1 Churchcrm | 2025-03-17 | N/A | 9.1 CRITICAL |
ChurchCRM 5.5.0 FRCertificates.php is vulnerable to Blind SQL Injection (Time-based) via the CurrentFundraiser GET parameter. | |||||
CVE-2024-25892 | 1 Churchcrm | 1 Churchcrm | 2025-03-17 | N/A | 8.1 HIGH |
ChurchCRM 5.5.0 ConfirmReport.php is vulnerable to Blind SQL Injection (Time-based) via the familyId GET parameter. | |||||
CVE-2024-25891 | 1 Churchcrm | 1 Churchcrm | 2025-03-17 | N/A | 7.5 HIGH |
ChurchCRM 5.5.0 FRBidSheets.php is vulnerable to Blind SQL Injection (Time-based) via the CurrentFundraiser GET parameter. | |||||
CVE-2023-27059 | 1 Churchcrm | 1 Churchcrm | 2025-02-26 | N/A | 5.4 MEDIUM |
A cross-site scripting (XSS) vulnerability in the Edit Group function of ChurchCRM v4.5.3 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the Edit Group Name text field. | |||||
CVE-2025-1024 | 1 Churchcrm | 1 Churchcrm | 2025-02-25 | N/A | 4.8 MEDIUM |
A vulnerability exists in ChurchCRM 5.13.0 that allows an attacker to execute arbitrary JavaScript in a victim's browser via Reflected Cross-Site Scripting (XSS) in the EditEventAttendees.php page. This requires Administration privileges and affects the EID parameter. The flaw allows an attacker to steal session cookies, perform actions on behalf of an authenticated user, and gain unauthorized access to the application. | |||||
CVE-2025-1132 | 1 Churchcrm | 1 Churchcrm | 2025-02-25 | N/A | 8.8 HIGH |
A time-based blind SQL Injection vulnerability exists in the ChurchCRM 5.13.0 and prior EditEventAttendees.php within the EN_tyid parameter. The parameter is directly inserted into an SQL query without proper sanitization, allowing attackers to inject malicious SQL commands. Please note that the vulnerability requires Administrator permissions. This flaw can potentially allow attackers to delay the response, indicating the presence of an SQL injection vulnerability. While it is a time-based blind injection, it can be exploited to gain insights into the underlying database, and with further exploitation, sensitive data could be retrieved. | |||||
CVE-2025-1133 | 1 Churchcrm | 1 Churchcrm | 2025-02-25 | N/A | 7.2 HIGH |
A vulnerability exists in ChurchCRM 5.13.0 and prior that allows an attacker to execute arbitrary SQL queries by exploiting a boolean-based blind SQL Injection vulnerability in the EditEventAttendees functionality. The EID parameter is directly concatenated into an SQL query without proper sanitization, making it susceptible to SQL injection attacks. An attacker can manipulate the query, potentially leading to data exfiltration, modification, or deletion. Please note that this vulnerability requires Administrator privileges. | |||||
CVE-2025-1134 | 1 Churchcrm | 1 Churchcrm | 2025-02-25 | N/A | 7.2 HIGH |
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 DonatedItemEditor 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 that this vulnerability requires Administrator privileges. |