dbcve.org
ChurchcrmApplication

CVE-2026-39340

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, a SQL injection vulnerability exists in PropertyTypeEditor.php, part of the administration functionality for managing property type categories (People → Person Properties / Family Properties). The vulnerability was introduced when legacyFilterInput() which both strips HTML and escapes SQL — was replaced with sanitizeText(), which strips HTML only. User-supplied values from the Name and Description fields are concatenated directly into raw INSERT and UPDATE queries with no SQL escaping. This allows any authenticated user with the MenuOptions role (a non-admin staff permission) to perform time-based blind injection and exfiltrate any data from the database, including password hashes of all users. 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 PropertyTypeEditor.php where the sanitizeText() function (which only strips HTML) replaced legacyFilterInput() (which also escaped SQL). User-supplied Name and Description fields are concatenated directly into raw INSERT/UPDATE queries, allowing authenticated users with the MenuOptions role to perform time-based blind SQL injection and exfiltrate sensitive data including password hashes.

MitigationUpgrade to ChurchCRM version 7.1.0 or later, which includes the fix. Alternatively, implement proper SQL parameterization (prepared statements) or add SQL escaping back to the input handling for these fields.

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
None

CVSS:3.1/AV:N/AC:L/PR:L/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 ChurchCRM installation version
    Locate the ChurchCRM version file (commonly version.php or similar in the root directory) and read the version number. Alternatively, check the database for version information if accessible.
    Affected if The installed version is below 7.1.0 (any version prior to 7.1.0 is affected)
  2. Locate PropertyTypeEditor.php file
    Search the web root directory for the file PropertyTypeEditor.php. Common paths may include /PropertyTypeEditor.php or within the /include or /modules directories.
    Affected if The file exists in the application directory (indicating the vulnerable component is present)
  3. Examine SQL query construction in PropertyTypeEditor.php
    Open PropertyTypeEditor.php and search for INSERT or UPDATE statements that concatenate the Name or Description fields directly into SQL queries without using prepared statements or parameter binding.
    Affected if Raw SQL concatenation is found for Name or Description fields (saniitizeText() is used instead of legacyFilterInput() or prepared statements)
  4. Check for authenticated users with MenuOptions role
    Query the database users table or role assignments to identify if any user account has the MenuOptions role assigned.
    Affected if Any user account with MenuOptions role exists in the system (this role enables access to the vulnerable Property Type Editor functionality)

You are affected if your ChurchCRM version is below 7.1.0, the PropertyTypeEditor.php file contains unsanitized SQL concatenation for Name/Description fields, and at least one user with the MenuOptions role can access that editor.

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 includes the fix. Alternatively, implement proper SQL parameterization (prepared statements) or add SQL escaping back to the input handling for these fields.

Recommended fix High confidence

7.1.0

  1. 1. Create a complete backup of the ChurchCRM database and application files before proceeding
  2. 2. Download ChurchCRM version 7.1.0 from the official GitHub repository (github.com/ChurchCRM/CRM)
  3. 3. Replace all application files with the new version 7.1.0 files, preserving any local configuration
  4. 4. Run any database migration scripts included in the 7.1.0 release
  5. 5. Clear any application caches if applicable
  6. 6. Verify the upgrade by logging in and checking that PropertyTypeEditor.php (People → Person Properties / Family Properties) functions correctly
  7. 7. Confirm the fix by verifying that Name and Description fields are properly handled (sanitized and escaped)

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

Fix this in Churchcrm Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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