dbcve.org
ChurchcrmApplication

CVE-2026-39337

CRITICAL · 10.0 CVSS v3.1 Published 2026-04-07
Fix available
A fix is available. Upgrade to 7.1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
ChurchCRM is an open-source church management system. Prior to 7.1.0, critical pre-authentication remote code execution vulnerability in ChurchCRM's setup wizard allows unauthenticated attackers to inject arbitrary PHP code during the initial installation process, leading to complete server compromise. The "$dbPassword" variable is not sanitized. This vulnerability exists due to an incomplete fix for CVE-2025-62521. This vulnerability is fixed in 7.1.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

ChurchCRM versions prior to 7.1.0 contain a critical pre-authentication remote code execution vulnerability in the setup wizard. The $dbPassword variable is not sanitized during the initial installation process, allowing unauthenticated attackers to inject arbitrary PHP code. This is an incomplete fix for CVE-2025-62521 and leads to complete server compromise.

MitigationUpgrade ChurchCRM to version 7.1.0 or later. Since this vulnerability is exploited during the initial setup wizard, ensure any already-deployed instances are immediately patched and the setup directory is restricted or removed post-installation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChurchcrmApplication
Affected:< 7.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify ChurchCRM installation
    Locate the ChurchCRM installation directory on the server. Look for typical paths such as /var/www/html/churchcrm, /var/www/churchcrm, or the web root directory. Identify the main index.php or configuration files to confirm this is a ChurchCRM installation.
    Affected if The software is ChurchCRM and the installation directory can be located on the server.
  2. Determine installed version
    Open the version file in the ChurchCRM installation directory. Common locations include version.php, include/version.php, or check composer.json for the 'version' or 'require' entry referencing 'churchcrm'. Extract the version number displayed.
    Affected if The installed version number is lower than 7.1.0 (for example, 7.0.x, 6.x.x, or any version prior to 7.1.0).
  3. Verify setup wizard accessibility
    Check if the setup directory exists and is accessible via web browser by navigating to /setup, /install, or /setupwizard within the ChurchCRM web path. Attempt to access the setup page without authentication.
    Affected if The setup wizard page loads without requiring authentication, indicating the setup process is still accessible.
  4. Check for post-installation cleanup
    Inspect the setup directory within the ChurchCRM installation (commonly /setup or /install folder). Determine whether the directory has been removed or restricted after initial installation by checking for the existence of the setup files.
    Affected if The setup directory and its files (such as index.php, setup1.php, or database.php within the setup folder) still exist on the server and are web-accessible.

A server is affected if ChurchCRM is installed with a version lower than 7.1.0 AND the setup wizard directory remains accessible on the web server without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.1.0 or later
Fixed in 7.1.0
Interim mitigation

Upgrade ChurchCRM to version 7.1.0 or later. Since this vulnerability is exploited during the initial setup wizard, ensure any already-deployed instances are immediately patched and the setup directory is restricted or removed post-installation.

Recommended fix High confidence

7.1.0

  1. Backup your current ChurchCRM installation and database before proceeding
  2. Download ChurchCRM version 7.1.0 from the official GitHub releases page (github.com/ChurchCRM/CRM/releases)
  3. Replace all existing ChurchCRM files with the files from version 7.1.0
  4. If prompted, run any database migration scripts included in the 7.1.0 release
  5. Verify the application functions correctly after the upgrade
  6. Ensure the setup wizard is not publicly accessible (consider restricting /setup or /install paths via web server configuration)
Caveat Minimal risk - this is a security patch release; however, always test in a staging environment before deploying to production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Churchcrm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39337 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-39337 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data