CVE-2026-39340: ChurchCRM is an open-source church management system. Prior to 7.1.0, a SQL injection vulnerability exists in…

CVE-2026-39340 · Severity: high · CVSS 8.1 · Published 2026-04-07

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.

Technologies: ChurchCRM. Vendors: ChurchCRM.

Quick answers

Is CVE-2026-39340 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-39340 being exploited in the wild.
How severe is CVE-2026-39340?
High severity, with a CVSS score of 8.1, published 7 April 2026.
Which products and versions are affected?
ChurchCRM. The advisory does not name versions.
Is there a fix for CVE-2026-39340?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2026-39340?
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.

Affected products

  • ChurchCRM

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.