dbcve.org
ChurchcrmApplication

CVE-2026-39326

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 /PropertyTypeEditor.php in ChurchCRM. Authenticated users with the role isMenuOptionsEnabled can inject arbitrary SQL statements through the Name and Description parameters 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 /PropertyTypeEditor.php endpoint allows authenticated users with the isMenuOptionsEnabled role to inject arbitrary SQL via the Name and Description parameters, enabling extraction or modification of database contents.

MitigationUpgrade to ChurchCRM 7.1.0 or later to obtain the security patch; until patched, limit the isMenuOptionsEnabled role to highly trusted users only.

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 or check the About page in the ChurchCRM interface. Common paths include /Version.txt, /include/config.php (version constant), or the admin dashboard.
    Affected if The installed version is below 7.1.0 (e.g., 7.0.x, 6.x.x, or earlier)
  2. Verify PropertyTypeEditor.php exists
    Check if the file /PropertyTypeEditor.php exists in the web root or served directory of the ChurchCRM installation.
    Affected if The file exists and the application version is below 7.1.0
  3. Confirm user role configuration
    Access the user management or role settings in ChurchCRM admin panel. Check if any user accounts are assigned the 'isMenuOptionsEnabled' role or equivalent menu management permission.
    Affected if Users exist with isMenuOptionsEnabled role and the application version is below 7.1.0
  4. Review application logs for suspicious requests
    Examine web server access logs and ChurchCRM application logs for POST requests to /PropertyTypeEditor.php containing unusual SQL syntax in Name or Description parameters.
    Affected if Log entries show SQL injection patterns in Name/Description parameters and the version is below 7.1.0

The environment is affected if ChurchCRM version is below 7.1.0, the PropertyTypeEditor.php endpoint is accessible, and users with isMenuOptionsEnabled role can submit Name or Description parameters that could contain SQL syntax.

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 7.1.0 or later to obtain the security patch; until patched, limit the isMenuOptionsEnabled role to highly trusted users only.

Recommended fix High confidence

ChurchCRM 7.1.0

  1. Backup the ChurchCRM database and all application files.
  2. Download ChurchCRM version 7.1.0 from the official release channel (e.g., GitHub releases).
  3. Extract and deploy the new files, replacing the existing application installation.
  4. Execute the database upgrade script (typically found at /Upgrade.php) to apply necessary schema changes.
  5. Verify the fix by logging in and confirming the /PropertyTypeEditor.php endpoint functions correctly and the vulnerability is resolved.
Caveat Standard minor version upgrade; ensure backups are verified and test in a non-production environment before deploying.

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

Fix this in Churchcrm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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