External risk intelligence

ChurchCRM SQL Injection Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-39342

ChurchCRM is a web-based application that may be hosted publicly for member access or kept behind internal access controls. While it is a web application, the specific functionality described requires an authenticated user with access to administrative or reporting modules, making broad, unauthenticated public internet exposure less typical than for a public-facing edge service or gateway.

SQL Injection

Churchcrm

before 7.1.0

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory describes a critical vulnerability in ChurchCRM, an open-source church management system, that could allow an authenticated user to inject malicious SQL code through its advanced search feature. If exploited, this could lead to unauthorized access, modification, or deletion of sensitive church data. The issue has been addressed in version 7.1.0.

  • SQL injection risk in church management software.
  • Authenticated users can potentially access sensitive data.
  • Confirm relevance and exposure to ChurchCRM installations.

Attack Path

How an attacker could exploit the issue

An attacker with authenticated access to ChurchCRM could exploit a SQL injection vulnerability to access or modify sensitive church data. This attack begins by logging into the system and navigating to the "Advanced Search" feature within the Data/Reports section. By manipulating the `searchwhat` parameter in a specific query, the attacker can inject malicious SQL code, leading to unauthorized data access or manipulation.

  • Authenticated user access required.
  • Malicious input targets search parameter.
  • Risk of data compromise or alteration.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, an authenticated user with specific access to reporting features could exploit a SQL injection vulnerability in ChurchCRM. This could potentially allow unauthorized access to sensitive church member data or alter system behavior related to queries.

  • Church member data.
  • SQL injection via advanced search.
  • Unauthorized data access or modification.

Operational Fix

Recommended remediation, mitigation, and detection steps

Application owners are likely responsible for ChurchCRM, as it's a self-hosted application requiring authenticated access to specific modules for exploitation. The first practical move is to identify all ChurchCRM instances, confirm their reachability and business criticality, and then engage the system's accountable owner to plan remediation based on risk.

  • Identify ChurchCRM instances and owners.
  • Verify user access and data criticality.
  • Plan vendor-coordinated updates.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is ChurchCRM?

ChurchCRM is an open-source software platform designed to help religious organizations manage their daily operations. It typically serves as a centralized hub for storing member records, tracking donations, organizing events, and handling internal communication. Because it manages significant amounts of personal and sensitive community data, it functions as a core administrative database for its users.

What is the CVE-2026-39342 SQL injection vulnerability?

This is a security flaw where an attacker can manipulate database queries by providing malicious input. Categorized as CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), the vulnerability allows unauthorized users to inject commands into the system's search functionality. This can potentially bypass standard security controls, allowing the attacker to view, change, or delete the sensitive data stored within the church's management database.

How is the CVE-2026-39342 vulnerability triggered?

Exploitation requires an attacker to be a logged-in user who has specific permissions to reach the 'Advanced Search' feature located within the 'Data/Reports' > 'Query Menu' section. By specifically targeting the 'searchwhat' parameter while running a query with 'QueryID=15', the attacker can trigger the flaw. Simply browsing the site or accessing public pages without this specific level of authenticated reporting access will not trigger the vulnerability.

Is my instance of ChurchCRM at risk?

According to Halo Surface Signal, risk depends on how your instance is hosted and who has access. While ChurchCRM is a web application, this specific flaw requires authenticated access to reporting modules, making it less likely to be exploited by unauthenticated internet users. You should evaluate whether your instance is exposed to the public internet or if it is restricted to internal users, as both scenarios still require addressing the underlying software flaw.

How do I respond to this ChurchCRM advisory?

Your first step is to identify all deployed instances of ChurchCRM within your organization to understand their location and business use. Once you have a complete inventory, verify the current version of each instance. If you are running any version prior to 7.1.0, you should coordinate with your system owners to schedule an update to 7.1.0 or newer, which contains the official fix for this vulnerability.

References