ChurchcrmApplication

CVE-2026-39343

HIGH · 7.2 CVSS v3.1 Published 2026-04-07
Fix available
A fix is available. Upgrade to 7.1.0 or later.
See remediation →
78/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 the EditEventTypes.php file, which is only accessible to administrators. The EN_tyid POST parameter is not sanitized before being used in a SQL query, allowing an administrator to execute arbitrary SQL commands directly against 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 EditEventTypes.php allows administrators to execute arbitrary SQL commands via the unsanitized EN_tyid POST parameter. This is a direct SQLi in an admin-only endpoint.

MitigationUpgrade to ChurchCRM version 7.1.0 or later, which contains the fix for proper input sanitization on the EN_tyid parameter.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Identify ChurchCRM installation
    Locate the ChurchCRM web application directory. Check for presence of index.php, Include/Config.php, or composer.json in the web root.
    Affected if ChurchCRM is not found in the environment, this CVE does not apply.
  2. Determine installed ChurchCRM version
    Open the version file or check the admin interface for the version number. Common locations: /docs/changelog.md, /Version.txt, or the admin dashboard.
    Affected if The installed version is less than 7.1.0, indicating the vulnerable code is present.
  3. Verify EditEventTypes.php exists
    Check for the presence of EditEventTypes.php in the web directory, typically under /events/ or the main ChurchCRM root.
    Affected if The file exists in the installation, a necessary component for this vulnerability to be exploited.
  4. Confirm administrator access is possible
    Verify that administrator user accounts can access the ChurchCRM admin panel and reach the Event Types management page.
    Affected if Authenticated administrator access exists, the SQL injection via EN_tyid parameter can be triggered.

The environment is affected if ChurchCRM version is below 7.1.0, EditEventTypes.php is accessible, and an administrator can authenticate to trigger the unsanitized EN_tyid parameter in SQL queries.

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 for proper input sanitization on the EN_tyid parameter.

Recommended fix High confidence

7.1.0

  1. Backup your ChurchCRM database before proceeding with any upgrade
  2. Download ChurchCRM version 7.1.0 from the official repository or release channel
  3. Follow the standard ChurchCRM upgrade procedure for your deployment method (manual or package-based)
  4. After upgrade, verify that the EditEventTypes.php file has been updated and EN_tyid parameter is now properly sanitized
  5. Test that Event Types functionality works correctly post-upgrade
Caveat Review release notes for 7.1.0 for any configuration or feature changes that may affect your deployment

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-39343 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-39343 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