# CVE-2026-39343: ChurchCRM SQL injection in EditEventTypes.php

Source: https://junglewise.ai/threats/cve-2026-39343-churchcrm-sql-injection-in-editeventtypes-php  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-07. Updated: 2026-07-24  
License: CC BY 4.0 with a link back

CVE-2026-39343 · Severity: high · CVSS 7.2 · Published 2026-04-07

ChurchCRM, an open-source church management system, contains a security flaw in its event type editor. An authorized administrator can execute unauthorized database commands by submitting specially crafted data. This could lead to the theft of sensitive member data, full database deletion, or potential takeover of the underlying server.

Technologies: [ChurchCRM](https://junglewise.ai/threats/technologies/churchcrm). Vendors: [ChurchCRM](https://junglewise.ai/threats/vendors/churchcrm).

## Quick answers

**Is CVE-2026-39343 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-39343 being exploited in the wild.

**How severe is CVE-2026-39343?** High severity, with a CVSS score of 7.2, published 7 April 2026.

**Which products and versions are affected?** ChurchCRM CRM < 7.1.0.

**Is there a fix for CVE-2026-39343?** A patch was published on 2026-04-07: Fix released in version 7.1.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-39343 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-39343?** Check whether you run ChurchCRM. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A SQL injection vulnerability exists in ChurchCRM's 'EditEventTypes.php' component due to improper neutralization of the 'EN_tyid' POST parameter. The application directly concatenates this parameter into a SQL query string without sanitization or prepared statements. While the exploit requires administrative privileges, a successful attack allows for arbitrary SQL execution against the backend database. This can result in full data exfiltration, unauthorized modification of records, or potential remote code execution via database features like 'INTO OUTFILE'. The issue is resolved in version 7.1.0.

## Affected products

- ChurchCRM CRM < 7.1.0

## Timeline

- 2026-04-05: advisory: GitHub Security Advisory published
- 2026-04-07: disclosed: CVE-2026-39343 published to NVD
- 2026-04-07: patched: Fix released in version 7.1.0

## References

- [https://github.com/ChurchCRM/CRM/security/advisories/GHSA-h2hx-p9gp-q7gr](https://github.com/ChurchCRM/CRM/security/advisories/GHSA-h2hx-p9gp-q7gr)

## Related threats

- [ChurchCRM CRM authorization bypass in family-scoped endpoints](https://junglewise.ai/threats/cve-2026-58410-churchcrm-crm-authorization-bypass-in-family-scoped-endpoints)
- [ChurchCRM unrestricted file upload in plugin installer](https://junglewise.ai/threats/cve-2026-58409-churchcrm-unrestricted-file-upload-in-plugin-installer)
- [ChurchCRM broken access control in CSVCreateFile.php export](https://junglewise.ai/threats/cve-2026-58408-churchcrm-broken-access-control-in-csvcreatefile-php-export)
- [ChurchCRM CSRF in legacy delete endpoints](https://junglewise.ai/threats/cve-2026-44548-churchcrm-csrf-in-legacy-delete-endpoints)
- [ChurchCRM 2FA and account lockout bypass in public API login](https://junglewise.ai/threats/cve-2026-44547-churchcrm-2fa-and-account-lockout-bypass-in-public-api-login)