dbcve.org
ChurchcrmApplication

CVE-2026-39330

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 /PropertyAssign.php in ChurchCRM. Authenticated users with the role Manage Groups & Roles (ManageGroups) and Edit Records (isEditRecordsEnabled) can inject arbitrary SQL statements through the Value 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 /PropertyAssign.php endpoint allows authenticated users with 'Manage Groups & Roles' and 'Edit Records' permissions to inject arbitrary SQL statements through the Value parameter, enabling unauthorized data extraction or modification.

MitigationUpgrade to ChurchCRM version 7.1.0 or later which contains the fix. Until then, restrict user permissions for the ManageGroups and isEditRecordsEnabled roles to limit exposure.

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. Check installed ChurchCRM version
    Locate the version file in the ChurchCRM installation directory, typically found in a version.php or config file, or access the admin dashboard System Settings page to view the version number.
    Affected if The installed version is any version before 7.1.0 (e.g., 7.0.x, 6.x.x, etc.)
  2. Verify PropertyAssign.php exists
    Check if the file /PropertyAssign.php exists in the web root of the ChurchCRM installation and is accessible via HTTP.
    Affected if The file exists and the application version is below 7.1.0
  3. Identify users with Manage Groups & Roles permission
    Navigate to Admin > Users and Roles, or query the database user_perms or group_member tables to list accounts with the Manage Groups permission or role assigned.
    Affected if Any authenticated user account has the Manage Groups & Roles permission enabled
  4. Identify users with Edit Records permission
    Navigate to Admin > Users and Roles, or query the database user_perms table to list accounts with the Edit Records permission assigned.
    Affected if Any authenticated user account has the Edit Records permission enabled
  5. Confirm intersection of both permissions
    Review the user permission list to determine if any single user account has BOTH Manage Groups & Roles AND Edit Records permissions simultaneously.
    Affected if At least one user account possesses both permissions, and the ChurchCRM version is below 7.1.0

A user is affected if their ChurchCRM installation is version 7.0.x or lower AND at least one authenticated user has both Manage Groups & Roles and Edit Records permissions, allowing them to exploit the SQL injection in PropertyAssign.php.

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 version 7.1.0 or later which contains the fix. Until then, restrict user permissions for the ManageGroups and isEditRecordsEnabled roles to limit exposure.

Recommended fix High confidence

7.1.0

  1. Create a complete backup of the ChurchCRM database and all application files
  2. Download ChurchCRM version 7.1.0 from the official source (github.com/ChurchCRM/CRM)
  3. Replace the existing ChurchCRM application files with the new version 7.1.0 files
  4. Review and run any included database migration scripts if present in the upgrade package
  5. Verify the application is functioning correctly after the upgrade
  6. Confirm the /PropertyAssign.php endpoint is accessible only to authorized users with appropriate role-based access controls
Caveat Review release notes for 7.1.0 to check for any configuration or feature changes that may affect existing integrations or customizations

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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