dbcve.org
ChurchcrmApplication

CVE-2026-39325

HIGH · 7.2 CVSS v3.1 Published 2026-04-07
Fix available
A fix is available. Upgrade to 7.1.0 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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, an SQL injection vulnerability was found in the endpoint /SettingsUser.php in ChurchCRM 7.0.5. Authenticated administrative users can inject arbitrary SQL statements through the type array parameter via the index and thus extract and modify information from the database. 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

SQL injection vulnerability in ChurchCRM's /SettingsUser.php endpoint allows authenticated administrative users to inject arbitrary SQL statements through the 'type array' parameter via the index parameter, enabling extraction and modification of database information.

MitigationUpgrade ChurchCRM to version 7.1.0 or later, which contains the fix for this SQL injection vulnerability.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/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 version
    Locate the version file or check the application metadata (commonly found in version.php, composer.json, or the admin dashboard About section) and note the exact version number
    Affected if The installed version is lower than 7.1.0
  2. Verify SettingsUser.php endpoint exists
    Check for the presence of /SettingsUser.php in the web root or source directory of the ChurchCRM installation
    Affected if The file exists and is accessible via the web server
  3. Confirm administrative access is possible
    Verify that admin-level user accounts can be created or already exist in the system, and that admin authentication is functional
    Affected if Administrative users can log in to the ChurchCRM system
  4. Check for type array parameter usage
    Inspect the request handling in SettingsUser.php or any accessible logs for usage of the 'type array' parameter through the 'index' parameter
    Affected if The application processes array-type parameters via the index parameter in SettingsUser.php

The environment is likely affected if ChurchCRM version is below 7.1.0, the SettingsUser.php endpoint exists, administrative authentication is possible, and the vulnerable parameter handling is in use.

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, which contains the fix for this SQL injection vulnerability.

Recommended fix High confidence

7.1.0

  1. 1. Back up the existing ChurchCRM installation directory and database before proceeding with the upgrade
  2. 2. Download ChurchCRM version 7.1.0 from the official GitHub repository (github.com/ChurchCRM/CRM)
  3. 3. Extract the downloaded archive and replace the existing ChurchCRM files with the new version 7.1.0 files
  4. 4. If there are database migration scripts provided in the release, run them to update the database schema
  5. 5. Clear any application caches if applicable
  6. 6. Verify the upgrade by logging in as an administrative user and confirming the application functions correctly
  7. 7. Test that the /SettingsUser.php endpoint no longer accepts malicious SQL input through the type array parameter
Caveat Review the release notes for 7.1.0 to check for any configuration or feature changes that may require adjustment

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39325 — 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-39325 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