CVE-2026-40482
SQL Injection in ChurchCRM FinancialService Allows Data Exposure
Publication date: 2026-04-18
Last updated on: 2026-04-18
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| churchcrm | churchcrm | to 7.2.0 (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
What immediate steps should I take to mitigate this vulnerability?
The vulnerability in ChurchCRM versions prior to 7.2.0 is caused by SQL injection in FinancialService::getMemberByScanString() due to unsanitized input.
To mitigate this vulnerability immediately, upgrade ChurchCRM to version 7.2.0 or later where this issue has been fixed.
Can you explain this vulnerability to me?
This vulnerability is a SQL injection issue found in ChurchCRM, an open-source church management system. Versions before 7.2.0 have a flaw in the FinancialService::getMemberByScanString() function where an unsanitized variable ($routeAndAccount) is directly concatenated into a SQL query. This allows an attacker to manipulate the SQL query, potentially leading to unauthorized database access or data manipulation.
How can this vulnerability impact me? :
The SQL injection vulnerability can allow an attacker with limited privileges to execute arbitrary SQL commands on the database. This can lead to unauthorized access to sensitive data, data corruption, or disruption of the application’s normal operation. Since the vulnerability is exploitable remotely without user interaction, it poses a significant security risk.