CVE-2025-66396
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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows a malicious or compromised administrator to execute arbitrary SQL commands, potentially leading to unauthorized access, modification, or deletion of sensitive data including user credentials, financial records, and personal information. Such unauthorized data exposure or manipulation could result in non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access and ensuring data integrity and confidentiality. [1]
Can you explain this vulnerability to me?
This vulnerability is a SQL injection flaw in ChurchCRM's UserEditor component (specifically in src/UserEditor.php) prior to version 6.5.3. When an administrator saves user configuration settings, the keys of the POST parameter array 'type' are not properly sanitized or validated before being used in SQL queries. The code extracts the array key and directly concatenates it into SELECT and UPDATE SQL statements without any checks. This allows a malicious or compromised administrator to inject arbitrary SQL commands, including time-based blind SQL injection attacks, to manipulate the database. [1]
How can this vulnerability impact me? :
If exploited by a malicious or compromised administrator, this vulnerability allows execution of arbitrary SQL queries on the database. This can lead to unauthorized access, modification, or deletion of all data, including user credentials, financial records, and personal information. It can also bypass application-level logging or restrictions and potentially lead to further system compromise, such as writing files to the server, depending on database permissions. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by attempting a time-based blind SQL injection using crafted POST requests targeting the `type` parameter keys. For example, sending a POST request with a payload like `&type[1+AND+SLEEP(5)--+]=text` to the vulnerable endpoint will cause a delay in the server response if the system is vulnerable. Monitoring for unusual delays or anomalies in response times when saving user configuration settings as an administrator can indicate exploitation attempts. Specific commands involve using tools like curl or Burp Suite to send such crafted POST requests to the UserEditor.php endpoint. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to upgrade ChurchCRM to version 6.5.3 or later, where this SQL injection vulnerability in `src/UserEditor.php` has been patched. Additionally, restrict administrator access to trusted users only, monitor administrator activities closely, and consider applying web application firewall (WAF) rules to detect and block suspicious SQL injection patterns in POST requests. Avoid using vulnerable versions in production environments. [1]