# CVE-2026-40582: ChurchCRM: Authentication Bypass in `/api/public/user/login` Allows Bypass of 2FA and Account Lockout

> Attackers can bypass 2FA and account lockout via the public login API to gain unauthorized access to protected endpoints.

- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Apr 2026
- **Updated:** 20 Apr 2026
- **Also known as:** GHSA-8cwr-x83m-mh9x

## What is CVE-2026-40582?

CVE-2026-40582 is a critical authentication bypass vulnerability in ChurchCRM CRM, published on 17 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. In versions prior to 7.2.0, the /api/public/user/login endpoint validates only the username and password before returning the user's API key, bypassing the normal authentication flow that enforces account lockout and two-factor authentication checks. An attacker with knowledge of a user's password can obtain API access even when the account is locked or has 2FA enabled, granting direct access to all protected API endpoints with that user's privileges. This issue has been fixed in version 7.2.0. Note: this issue had a duplicate, GHSA-472m-p3gf-46xp, which has been closed.

Weakness: CWE-305 (Authentication Bypass by Primary Weakness), CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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


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

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

## Is CVE-2026-40582 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-40582 is a critical authentication bypass vulnerability in ChurchCRM CRM, published on 17 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-40582 exists.

Affected product: ChurchCRM CRM. 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-40582/ (Markdown: https://insights.sbomify.com/CVE-2026-40582/index.md)
```

## Sources

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

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