External risk intelligence

ChurchCRM Setup Wizard Pre-Authentication Code Execution Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 10.0)

CVE-2026-39337

ChurchCRM is a web application designed for management purposes. While the vulnerability specifically affects the setup wizard, such web-based management platforms are commonly deployed as internet-accessible applications, making the installation or management interface a frequent target for exposure.

Code Injection

Churchcrm

before 7.1.0

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory addresses a critical security flaw in the ChurchCRM software, a system used for managing church data. The vulnerability allows attackers to remotely execute code on servers during the initial setup phase, potentially leading to a complete compromise of the server. The issue stems from improperly handled input during the installation process, posing a significant risk to the confidentiality, integrity, and availability of the system and its data.

  • Flaw allows remote code execution during setup.
  • Critical flaw, impacts server security.
  • Confirm relevance and assess exposure.

Attack Path

How an attacker could exploit the issue

An attacker can gain control of a ChurchCRM server by exploiting a flaw in the setup wizard during installation. Because the database password input is not properly secured, an unauthenticated attacker can inject malicious PHP code, allowing them to run any command on the server.

  • Attacker can access setup wizard remotely.
  • Unsanitized input allows code injection.
  • Complete server compromise is possible.

Live Threat

Current exploitation, exposure, and threat context

During the initial installation of ChurchCRM, an unauthenticated attacker could inject arbitrary PHP code by exploiting a lack of sanitization in the database password variable. This could lead to the compromise of the entire server when the setup wizard is accessible.

  • Server code execution.
  • Unsanitized input during setup.
  • Complete server compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

The ChurchCRM application owner is responsible for addressing this vulnerability, as it impacts the core management system. The first step is to identify all instances of ChurchCRM, determine their accessibility and criticality, and then plan remediation.

  • Application owners must resolve.
  • Verify all ChurchCRM deployments.
  • Plan risk-based remediation efforts.

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 and how is it typically used?

ChurchCRM is an open-source web application designed to help organizations manage their church data, such as member records, financial contributions, and event scheduling. Because it functions as a centralized hub for sensitive administrative tasks, it is often hosted on web servers to allow authorized staff to manage operations from different locations.

What does CWE-94 mean in the context of CVE-2026-39337?

CWE-94 refers to Improper Control of Generation of Code. In this vulnerability, it means the software fails to properly filter the input provided during the setup process. Because the application blindly trusts the database password field, an attacker can input malicious PHP instructions instead of a password, which the server then executes as legitimate code.

How does an attacker trigger this remote code execution?

An attacker triggers this by interacting with the setup wizard during the initial installation phase of the software. The vulnerability is specifically tied to the processing of the database password variable. It is important to note that this is not a general flaw in the standard operation of an already-installed system; it is restricted to the specific conditions of the setup process.

Do I need to worry if my ChurchCRM instance is internal?

Halo Surface Signal indicates that because ChurchCRM is a web-based management platform, instances are frequently deployed with internet-facing access, making them common targets. If your instance is strictly internal, the risk is reduced, but the vulnerability remains critical for any server where the setup wizard is reachable by unauthorized users.

How should I respond to this ChurchCRM security advisory?

The primary response is to update your software to version 7.1.0 or later, which contains the necessary fix for this code injection flaw. Start by auditing your environment to locate all ChurchCRM deployments, confirm which versions are in use, and prioritize upgrading any instances that remain on vulnerable versions to prevent potential server compromise.

References