Quick answers
- Is CVE-2026-44548 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44548 being exploited in the wild.
- How severe is CVE-2026-44548?
- High severity, with a CVSS score of 8.1, published 12 May 2026.
- Which products and versions are affected?
- ChurchCRM <= 7.2.2.
- Is there a fix for CVE-2026-44548?
- 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.
- How is CVE-2026-44548 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-44548?
- Check whether you run ChurchCRM at an affected version. 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 Cross-Site Request Forgery (CSRF) vulnerability exists in ChurchCRM versions 7.2.2 and earlier due to the use of HTTP GET requests for destructive operations without CSRF token validation. The affected endpoints—FundRaiserDelete.php, PropertyTypeDelete.php, and NoteDelete.php—perform record deletions based solely on GET parameters and role-based authorization. Because the application's session cookies use 'SameSite=Lax' and the endpoints do not validate Origin, Referer, or Fetch-Metadata headers, an attacker can trigger these deletions via a top-level navigation (e.g., a link or window.location assignment) from a malicious site. Successful exploitation allows for the unauthorized deletion of fundraisers, notes, and property types, including cascaded deletions of associated records. The issue is resolved in version 7.3.2.
Affected products
- ChurchCRM ChurchCRM <= 7.2.2
Timeline
- 2026-05-01: advisory: GitHub Security Advisory published
- 2026-05-12: disclosed: CVE-2026-44548 published