Skip to main content
VulnerabilityPublished Updated

CVE-2026-39318: ChurchCRM CRM · SQL Injection

Affects ChurchCRM CRMSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 7.1.0 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 7.1.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade CRM and churchcrm/CRM to 7.1.0.

Affected software

ProductAffectedFixed in
ChurchCRMCRMAffected
  • <7.1.0
Fixed in
  • 7.1.0
GitHubchurchcrm/CRMpkg:github/churchcrm/CRMOther threatsAffected
  • <7.1.0
Fixed in
  • 7.1.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade ChurchCRM to version 7.1.0 or later, where this SQL injection vulnerability is fixed. No other official remediation or temporary fixes are indicated. Users should ensure that only trusted users have ManageGroups or administrative privileges to reduce risk until patched.

Description

ChurchCRM is an open-source church management system. Versions prior to 7.1.0 have an SQL injection vulnerability in the endpoints `/GroupPropsFormRowOps.php`, `/PersonCustomFieldsRowOps.php`, and `/FamilyCustomFieldsRowOps.php`. A user has to be authenticated. For `ManageGroups` privileges have to be enabled and for the other two endpoints the attack has to be executed by an administrative user. These users can inject arbitrary SQL statements through the `Field` parameter and thus modify tables from the database. This vulnerability is fixed in 7.1.0.

References

Community reviews

Loading reviews…