dbcve.org
ChurchcrmApplication

CVE-2026-39334

HIGH · 8.8 CVSS v3.1 Published 2026-04-07
Fix available
A fix is available. Upgrade to 7.1.0 or later.
See remediation →
94/100
Remediation priority · Urgent
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 /SettingsIndividual.php in ChurchCRM 7.0.5. Authenticated users without any specific privileges 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 /SettingsIndividual.php endpoint allows authenticated users to inject arbitrary SQL through the type array parameter via the index parameter, enabling extraction and modification of database contents.

MitigationUpgrade to ChurchCRM 7.1.0 or later to obtain the patched version. If immediate upgrade is not feasible, implement strict input validation and use parameterized queries as a compensating control.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 and version
    Locate the ChurchCRM installation directory and check the version file or composer.json for the installed version number
    Affected if The installed version is less than 7.1.0
  2. Verify the SettingsIndividual.php endpoint exists
    Check if the file /SettingsIndividual.php exists in the web root or source code of the ChurchCRM installation
    Affected if The file exists and the application is running a version below 7.1.0
  3. Confirm authentication is enabled
    Verify that the ChurchCRM user authentication system is active and accessible (check if login functionality is enabled in the configuration)
    Affected if User authentication is enabled and the application accepts authenticated sessions
  4. Check if type array parameter is accepted
    Review the SettingsIndividual.php source code to confirm it accepts a 'type' parameter as an array via index (e.g., type[0]=value)
    Affected if The endpoint accepts type array parameters and the application version is below 7.1.0
  5. Verify database connectivity
    Confirm the application has an active database connection and the web server can execute PHP scripts against the database
    Affected if The application is functional with database connectivity and the vulnerable endpoint is accessible

A user is affected if ChurchCRM version is below 7.1.0, the SettingsIndividual.php endpoint exists, and authenticated users can access the vulnerable type array parameter.

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 to ChurchCRM 7.1.0 or later to obtain the patched version. If immediate upgrade is not feasible, implement strict input validation and use parameterized queries as a compensating control.

Recommended fix High confidence

7.1.0

  1. 1. Create a complete backup of the ChurchCRM database and files before proceeding
  2. 2. Download ChurchCRM version 7.1.0 or later from the official repository (github.com/ChurchCRM/CRM)
  3. 3. Upgrade the ChurchCRM installation to version 7.1.0 following standard upgrade procedures
  4. 4. Verify the upgrade completed successfully by checking the application version
  5. 5. Test that the /SettingsIndividual.php endpoint functions correctly and that the SQL injection vulnerability is no longer present

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

Fix this in Churchcrm Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,790
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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