CVE-2026-39331 ChurchCRM has an API Authorization Bypass Allows Authenticated User to Deactivate, Modify, and Spam Arbitrary Families
Authenticated users can bypass authorization checks to modify, deactivate, or spam arbitrary family records in ChurchCRM.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-39331?
CVE-2026-39331 is a high-severity missing authorization vulnerability in Churchcrm Churchcrm, published on 7 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Which versions are affected by CVE-2026-39331?
It affects 1 product.
Products include Churchcrm Churchcrm.
How do I fix CVE-2026-39331?
No fix has been published for CVE-2026-39331 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-39331 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39331 exists.
Other vulnerabilities in Churchcrm Churchcrm
Sources
Also known as GHSA-vwh8-x823-wjc5.