dbcve.org
ChurchcrmApplication

CVE-2026-39331

HIGH · 8.1 CVSS v3.1 Published 2026-04-07
Fix available
A fix is available. Upgrade to 7.1.0 or later.
See remediation →
87/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 authenticated API user can modify any family record's state without proper authorization by simply changing the {familyId} parameter in requests, regardless of whether they possess the required EditRecords privilege. /family/{familyId}/verify, /family/{familyId}/verify/url, /family/{familyId}/verify/now, /family/{familyId}/activate/{status}, and /family/{familyId}/geocode lack role-based access control, allowing users to deactivate/reactivate arbitrary families, spam verification emails, and mark families as verified and trigger geocoding. 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 an IDOR vulnerability with missing function-level access control in five family API endpoints (/family/{familyId}/verify, /verify/url, /verify/now, /activate/{status}, and /geocode). Authenticated users can modify any family record's state without the required EditRecords privilege by simply changing the familyId parameter, allowing deactivation/reactivation of arbitrary families, spam verification emails, and triggering geocoding on unauthorized records.

MitigationUpgrade to ChurchCRM version 7.1.0 or later which implements proper role-based access control on the affected family API endpoints.

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
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 installed ChurchCRM version
    Locate the version file or check the database version metadata. Typically found in system info pages, a version.php file, or the database version table.
    Affected if The installed version is below 7.1.0 (e.g., 7.0.x, earlier releases)
  2. Verify user privilege configuration
    Check the logged-in user account permissions. Confirm whether the user lacks the EditRecords privilege in the user management or role configuration section.
    Affected if The user is authenticated but does NOT have the EditRecords privilege assigned
  3. Test API endpoint access without elevated privileges
    Using an authenticated session without EditRecords, make an HTTP request to /family/{familyId}/verify or /geocode endpoints with a familyId that differs from the user's own family record.
    Affected if The API returns a successful response (200 OK) instead of a 403 Forbidden or authorization error
  4. Confirm family modification capability
    Attempt to change a family record state (activate/deactivate) or trigger geocoding on a family ID that the unprivileged user does not own, using the vulnerable endpoints.
    Affected if The operation succeeds, indicating the IDOR vulnerability allows unauthorized modification

You are affected if ChurchCRM version is below 7.1.0 AND an authenticated user without EditRecords privilege can successfully modify or access family records via the API endpoints by manipulating the familyId 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 version 7.1.0 or later which implements proper role-based access control on the affected family API endpoints.

Recommended fix High confidence

7.1.0

  1. Backup the ChurchCRM database before proceeding with any upgrade
  2. Download ChurchCRM version 7.1.0 from the official GitHub repository (github.com/ChurchCRM/CRM)
  3. Extract and deploy the new version to your web server, replacing the existing installation
  4. Run any database migration scripts included in the 7.1.0 release
  5. Verify that the application runs without errors and all functionalities work correctly
  6. Test the previously vulnerable endpoints (/family/{familyId}/verify, /family/{familyId}/verify/url, /family/{familyId}/verify/now, /family/{familyId}/activate/{status}, /family/{familyId}/geocode) to confirm they now enforce proper authorization checks

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-39331 — 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-39331 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