CVE-2026-39317: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in ChurchCRM CRM
A SQL injection vulnerability exists in ChurchCRM versions prior to 7. 1. 0 in the SettingsIndividual. php file. The issue arises because user-controlled array keys from the POST parameter 'type' are used directly in SQL queries without proper sanitization. This flaw allows any authenticated user to extract sensitive data from the database. The vulnerability has a high severity with a CVSS score of 8. 8. It is fixed in version 7. 1.
AI Analysis
Technical Summary
ChurchCRM, an open-source church management system, contains a SQL injection vulnerability (CWE-89) in versions before 7.1.0. The vulnerability is located in SettingsIndividual.php where user input from the POST parameter 'type' is used as array keys directly in SQL commands without sanitization. This improper neutralization of special elements in SQL commands enables authenticated users to perform unauthorized data extraction from the database. The vulnerability is addressed and fixed in ChurchCRM version 7.1.0.
Potential Impact
Exploitation of this vulnerability allows any authenticated user to execute unauthorized SQL queries, potentially leading to disclosure of sensitive data, modification of data, and disruption of availability. The CVSS score of 8.8 indicates a high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
Upgrade ChurchCRM to version 7.1.0 or later, where this SQL injection vulnerability has been fixed. Since no official patch link or advisory is provided, users should verify the upgrade from the official ChurchCRM project sources. Patch status is not yet confirmed via vendor advisory; check the vendor's official channels for the latest remediation guidance.
CVE-2026-39317: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in ChurchCRM CRM
Description
A SQL injection vulnerability exists in ChurchCRM versions prior to 7. 1. 0 in the SettingsIndividual. php file. The issue arises because user-controlled array keys from the POST parameter 'type' are used directly in SQL queries without proper sanitization. This flaw allows any authenticated user to extract sensitive data from the database. The vulnerability has a high severity with a CVSS score of 8. 8. It is fixed in version 7. 1.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
ChurchCRM, an open-source church management system, contains a SQL injection vulnerability (CWE-89) in versions before 7.1.0. The vulnerability is located in SettingsIndividual.php where user input from the POST parameter 'type' is used as array keys directly in SQL commands without sanitization. This improper neutralization of special elements in SQL commands enables authenticated users to perform unauthorized data extraction from the database. The vulnerability is addressed and fixed in ChurchCRM version 7.1.0.
Potential Impact
Exploitation of this vulnerability allows any authenticated user to execute unauthorized SQL queries, potentially leading to disclosure of sensitive data, modification of data, and disruption of availability. The CVSS score of 8.8 indicates a high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
Upgrade ChurchCRM to version 7.1.0 or later, where this SQL injection vulnerability has been fixed. Since no official patch link or advisory is provided, users should verify the upgrade from the official ChurchCRM project sources. Patch status is not yet confirmed via vendor advisory; check the vendor's official channels for the latest remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-06T19:31:07.266Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69d5660baaed68159a5b4087
Added to database: 4/7/2026, 8:16:11 PM
Last enriched: 4/7/2026, 8:31:14 PM
Last updated: 4/7/2026, 10:28:56 PM
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.