# CVE-2026-39339: ChurchCRM has an API Authentication Bypass

> Unauthenticated attackers can bypass API authentication in ChurchCRM to access protected endpoints and expose sensitive member data.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Apr 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-v3p2-mx78-pxhc

## What is CVE-2026-39339?

CVE-2026-39339 is a critical authentication bypass vulnerability in Churchcrm Churchcrm, published on 7 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ChurchCRM is an open-source church management system. Prior to 7.1.0, a  critical authentication bypass vulnerability in ChurchCRM's API middleware (ChurchCRM/Slim/Middleware/AuthMiddleware.php) allows unauthenticated attackers to access all protected API endpoints by including "api/public" anywhere in the request URL, leading to complete exposure of church member data and system information. This vulnerability is fixed in 7.1.0.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Churchcrm Churchcrm.

## How do I fix CVE-2026-39339?

No fix has been published for CVE-2026-39339 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-39339 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39339 exists.

Public exploit code:

- ChurchCRM - API Authentication Bypass via URL Injection (nuclei): http/cves/2026/CVE-2026-39339.yaml

## 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-39339 and fix it if it is affected.

What it is: CVE-2026-39339 is a critical authentication bypass vulnerability in Churchcrm Churchcrm, published on 7 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39339 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-39339/ (Markdown: https://insights.sbomify.com/CVE-2026-39339/index.md)
```

## Sources

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

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