# 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.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Apr 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-vwh8-x823-wjc5

## 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.

Weakness: CWE-863 (Incorrect Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-39331?

It affects 1 product.


Products: 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.

## 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

- [CVE-2026-39337](https://insights.sbomify.com/CVE-2026-39337/): ChurchCRM Affected by Unauthenticated RCE in Install Wizard (critical 10.0)
- [CVE-2025-62521](https://insights.sbomify.com/CVE-2025-62521/): ChurchCRM has unauthenticated RCE in its Install Wizard (critical 10.0)
- [CVE-2025-68110](https://insights.sbomify.com/CVE-2025-68110/): ChurchCRM discloses database information on error message (critical 10.0)
- [CVE-2024-53438](https://insights.sbomify.com/CVE-2024-53438/): SQL injection in n/a (critical 9.8)
- [CVE-2024-25894](https://insights.sbomify.com/CVE-2024-25894/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-39331 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39331 exists.

Affected product: Churchcrm Churchcrm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-39331/ (Markdown: https://insights.sbomify.com/CVE-2026-39331/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-39331
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-39331
- OSV: https://osv.dev/vulnerability/CVE-2026-39331

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-39331/
Summaries are generated and may contain mistakes; the official description above is the record.