dbcve.org
ChurchcrmApplication

CVE-2026-39327

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 /MemberRoleChange.php in ChurchCRM 7.0.5. Authenticated users with the role Manage Groups & Roles (ManageGroups) can inject arbitrary SQL statements through the NewRole parameter 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 /MemberRoleChange.php endpoint allows authenticated users with the Manage Groups & Roles (ManageGroups) permission to inject arbitrary SQL through the NewRole parameter, enabling data extraction or modification from the database.

MitigationUpgrade ChurchCRM to version 7.1.0 or later, which contains the fix for proper input sanitization on the NewRole parameter.

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 web application files and check the version identifier (typically in a VERSION file, composer.json, or system info page). Compare the installed version number to the affected range: versions before 7.1.0.
    Affected if The installed ChurchCRM version is lower than 7.1.0
  2. Locate MemberRoleChange.php endpoint
    Find the file /MemberRoleChange.php within the ChurchCRM web directory. This is the vulnerable endpoint that handles member role changes.
    Affected if The file MemberRoleChange.php exists and is accessible within the web application
  3. Verify NewRole parameter handling
    Examine the MemberRoleChange.php source code to observe how the NewRole parameter is processed. Look for direct use of this parameter in SQL queries without proper sanitization or parameterized queries.
    Affected if The NewRole parameter is used directly in SQL queries without prepared statements or input sanitization
  4. Confirm ManageGroups permission exists
    Check the ChurchCRM user permissions system to determine if the ManageGroups permission (Manage Groups & Roles) is assigned to any user role or individual user account.
    Affected if There are users or roles granted the ManageGroups permission, enabling them to access the vulnerable endpoint

You are affected if ChurchCRM version is below 7.1.0, the MemberRoleChange.php endpoint exists, and users with ManageGroups permission can access it.

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 proper input sanitization on the NewRole parameter.

Recommended fix High confidence

7.1.0

  1. 1. Backup the current ChurchCRM database and files before proceeding with the upgrade
  2. 2. Download ChurchCRM version 7.1.0 or later from the official repository (github.com/ChurchCRM/CRM)
  3. 3. Upgrade the existing ChurchCRM installation to version 7.1.0 following the standard upgrade procedure
  4. 4. Verify the upgrade was successful by logging in and confirming the /MemberRoleChange.php endpoint functions correctly with the NewRole parameter

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

Fix this in Churchcrm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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