CVE-2026-39331: ChurchCRM is an open-source church management system. Prior to 7.1.0, an authenticated API user can modify any family…
CVE-2026-39331 · Severity: high · CVSS 8.1 · Published 2026-04-07
ChurchCRM is an open-source church management system. Prior to 7.1.0, an authenticated API user can modify any family record's state without proper authorization by simply changing the {familyId} parameter in requests, regardless of whether they possess the required EditRecords privilege. /family/{familyId}/verify, /family/{familyId}/verify/url, /family/{familyId}/verify/now, /family/{familyId}/activate/{status}, and /family/{familyId}/geocode lack role-based access control, allowing users to deactivate/reactivate arbitrary families, spam verification emails, and mark families as verified and trigger geocoding. This vulnerability is fixed in 7.1.0.
No. Junglewise Threat Intelligence has no report of CVE-2026-39331 being exploited in the wild.
How severe is CVE-2026-39331?
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-39331?
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-39331?
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.