External risk intelligence

ChurchCRM Backup Restore Path Traversal Leading to Code Execution.

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-35573

ChurchCRM is a web-based management application typically deployed as an internet-facing service to allow administrative access from various locations. While the vulnerability requires authenticated administrator access, the application itself is commonly exposed to the internet for remote management, making the interface reachable in typical deployments.

Path Traversal

Churchcrm

before 6.5.3

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 concerns a critical vulnerability in the ChurchCRM management system that could allow an authenticated administrator to execute arbitrary code on the server. The flaw is related to how file uploads are handled during the backup restore process, potentially enabling an attacker to overwrite critical configuration files.

  • Authenticated users could run unauthorized code.
  • Affects systems managing church operations and data.
  • Confirm if ChurchCRM is used and assess exposure.

Attack Path

How an attacker could exploit the issue

An attacker could gain control of a ChurchCRM server by exploiting a path traversal flaw in the backup restore feature. This would require the attacker to first gain administrator access to the system. Once authenticated, the attacker could upload a malicious file disguised as a backup, which could overwrite critical server configuration files and lead to remote code execution.

  • Authenticated administrator access required.
  • Upload arbitrary files via backup restore.
  • Remote code execution.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an authenticated administrator to upload arbitrary files, potentially leading to remote code execution by overwriting critical server configuration files. This could affect the integrity and availability of the ChurchCRM system and any data it manages.

  • System configuration files.
  • Uploading malicious files.
  • System compromise or data loss.

Operational Fix

Recommended remediation, mitigation, and detection steps

Application owners responsible for ChurchCRM instances should lead remediation efforts, coordinating with infrastructure teams for deployment and network/security teams for exposure assessment. The initial step involves identifying all ChurchCRM deployments, confirming their reachability and criticality, and then locating the accountable system owner to prioritize and schedule the fix.

  • Application owners are responsible.
  • Verify all ChurchCRM instance reachability.
  • Plan remediation in the next maintenance window.

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 web application designed to help religious organizations manage their daily operations, including member databases, donation tracking, and event scheduling. It is typically hosted on a web server to provide administrators with a centralized dashboard for managing these tasks.

What does CVE-2026-35573 mean for system security?

This vulnerability is classified as Improper Limitation of a Pathname (CWE-22) and Unrestricted Upload of File with Dangerous Type (CWE-434). In plain terms, the software fails to properly check file names during the backup restore process. This allows a user to upload files into unintended locations on the server, potentially overwriting server configuration files to run unauthorized code.

How is this vulnerability triggered?

An attacker must already have authenticated administrator access to the ChurchCRM dashboard to initiate the malicious backup restore. The vulnerability does not trigger through public or unauthenticated areas of the site; it specifically targets the functionality within the backup restoration system that handles uploaded files.

Is my ChurchCRM instance at risk?

According to Halo Surface Signal, ChurchCRM is often deployed as an internet-facing service to facilitate remote administrative management. If your instance is reachable via the internet, it is more accessible to potential attackers than one restricted to an internal-only network.

How do I secure my system against this vulnerability?

The primary response is to update your ChurchCRM software to version 6.5.3 or later, which contains the fix for this issue. Before applying the update, verify all your current ChurchCRM deployments, confirm who is responsible for managing each instance, and coordinate the update process with your technical team.

References