CVE-2025-66395
BaseFortify
Publication date: 2025-12-17
Last updated on: 2025-12-18
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| churchcrm | churchcrm | to 6.5.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a SQL injection flaw in ChurchCRM versions prior to 6.5.3, specifically in the file src/ListEvents.php. The issue arises because the WhichType POST parameter, used to filter event types, is not properly sanitized or type-casted before being used in SQL queries. This allows any authenticated user to inject arbitrary SQL commands, including time-based blind SQL injection attacks, by manipulating the WhichType parameter. As a result, attackers can execute unauthorized SQL queries on the database. [1]
How can this vulnerability impact me? :
This vulnerability can have severe impacts. Any authenticated user, regardless of privilege level, can execute arbitrary SQL queries on the database. This can lead to exfiltration, modification, or deletion of any data stored in the database, including sensitive information such as user credentials, financial data, and personal information. Ultimately, this can result in a full compromise of the application's data confidentiality, integrity, and availability. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by intercepting and modifying the POST request to the `ListEvents.php` file, specifically the `WhichType` parameter. A proof of concept involves sending a payload such as `1 AND IF(1=1, SLEEP(2), 0)` in the `WhichType` parameter. If the server response is delayed by the specified time (e.g., 2 seconds), it confirms the presence of the SQL injection vulnerability. You can use tools like curl or Burp Suite to send such POST requests and observe response times. Example curl command: `curl -X POST -d "WhichType=1 AND IF(1=1, SLEEP(2), 0)" https://yourchurchcrmserver/src/ListEvents.php` [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to upgrade ChurchCRM to version 6.5.3 or later, where the issue has been fixed. This update properly sanitizes and type-casts the `WhichType` parameter to prevent SQL injection. Until the upgrade can be applied, restrict authenticated user access to the vulnerable endpoint and monitor for suspicious activity involving the `WhichType` parameter. [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows any authenticated user to execute arbitrary SQL commands, potentially leading to exfiltration, modification, or deletion of sensitive data including user credentials, financial data, and personal information. This full compromise of the application's data could result in violations of data protection regulations such as GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access and breaches. [1]