dbcve.org
ChurchcrmApplication

CVE-2026-39339

CRITICAL · 9.1 CVSS v3.1 Published 2026-04-07
Fix available
A fix is available. Upgrade to 7.1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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, a critical authentication bypass vulnerability in ChurchCRM's API middleware (ChurchCRM/Slim/Middleware/AuthMiddleware.php) allows unauthenticated attackers to access all protected API endpoints by including "api/public" anywhere in the request URL, leading to complete exposure of church member data and system information. 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 authentication bypass in the API middleware (ChurchCRM/Slim/Middleware/AuthMiddleware.php) where including 'api/public' anywhere in the request URL allows unauthenticated attackers to bypass authentication and access all protected API endpoints, exposing sensitive church member data and system information.

MitigationUpgrade ChurchCRM to version 7.1.0 or later to remediate the authentication bypass 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

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
    Check the version.php file in the ChurchCRM root directory, or look for a version identifier in the admin panel under System Settings or About section. Common locations: include/Version.php or as a constant in config files.
    Affected if The installed version is any release prior to 7.1.0 (e.g., 7.0.x, 6.x.x, etc.)
  2. Verify AuthMiddleware.php exists
    Locate the file ChurchCRM/Slim/Middleware/AuthMiddleware.php in the web root. Inspect the file to see if it contains logic that checks for 'api/public' in the request path.
    Affected if The file exists and contains URL pattern matching that allows 'api/public' strings to bypass authentication checks.
  3. Confirm API endpoints are exposed
    Check if the Slim framework routes are configured to expose API endpoints. Look for index.php, slim/index.php, or similar entry points that route /api/ requests. Verify that API endpoints are accessible from the network (not blocked by firewall or authentication at the web server level).
    Affected if API endpoints (/api/... routes) are accessible without requiring prior authentication at the web server level.
  4. Test for authentication bypass
    Send a crafted request to any protected API endpoint (e.g., /api/persons, /api/families) with the string 'api/public' inserted anywhere in the URL path, for example: /api/public/../persons or /some/path/api/public/../persons. A successful bypass returns JSON data without providing any authentication token.
    Affected if The server returns valid JSON data containing church member information, family records, or system data without requiring authentication.

You are affected if ChurchCRM version is below 7.1.0 AND the API endpoints are network-accessible, as the AuthMiddleware.php flawed pattern matching allows any URL containing 'api/public' to bypass authentication.

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 to remediate the authentication bypass vulnerability.

Recommended fix High confidence

7.1.0

  1. 1. Backup the current ChurchCRM installation and database before proceeding with any upgrade
  2. 2. Download ChurchCRM version 7.1.0 from the official ChurchCRM repository (github.com/ChurchCRM/CRM) or official distribution channel
  3. 3. Replace/overwrite the existing ChurchCRM files with the new version 7.1.0 files
  4. 4. Run any database migration scripts if included in the upgrade package
  5. 5. Verify the upgrade was successful by logging into the administration interface
  6. 6. Test that protected API endpoints now require proper authentication (the vulnerability allowed bypass via 'api/public' in URL)

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

Fix this in Churchcrm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
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,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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