Skip to main content
VulnerabilityPublished Updated

CVE-2026-40581: ChurchCRM CRM · Cross-Site Request Forgery (CSRF)

Affects ChurchCRM CRMSource CVE Database V5

0

Not known to be exploited · CVSS 8.1 High : upgrade to 7.2.0 soon.

Data as of 28 Oct 2026, 05:11 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade CRM and churchcrm/CRM to 7.2.0.

Affected software

ProductAffectedFixed in
ChurchCRMCRMAffected
  • <7.2.0
Fixed in
  • 7.2.0
GitHubchurchcrm/CRMpkg:github/churchcrm/CRMOther threatsAffected
  • <7.2.0
Fixed in
  • 7.2.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.2.0 or later, where this vulnerability has been fixed by adding proper CSRF token validation to the deletion endpoint. Until upgraded, restrict access to the deletion functionality to trusted users and avoid visiting untrusted links while authenticated as an administrator. Patch status is not explicitly stated but the vendor fixed the issue in version 7.2.0.

Description

ChurchCRM is an open-source church management system. In versions prior to 7.2.0, the family record deletion endpoint (SelectDelete.php) performs permanent, irreversible deletion of family records and all associated data via a plain GET request with no CSRF token validation. An attacker can craft a malicious page that, when visited by an authenticated administrator, silently triggers deletion of targeted family records including associated notes, pledges, persons, and property data without any user interaction. This issue has been fixed in version 7.2.0.

References

Community reviews

Loading reviews…