# CVE-2026-44547: Auth bypass in CRM

> Attackers can bypass two-factor authentication and account lockout via the public API in ChurchCRM, potentially taking over accounts.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N`)
- **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:** 12 May 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-cwp8-rm8g-q5c9

## What is CVE-2026-44547?

CVE-2026-44547 is a critical authentication bypass vulnerability in ChurchCRM CRM, published on 12 May 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. From 7.2.0 to 7.2.2, The fix for CVE-2026-4058 is incomplete. The hardening commit was merged and then silently stripped from src/api/routes/public/public-user.php by an unrelated PR before any 7.2.x tag was cut. Every shipped 7.2.x release therefore remains exploitable by the PoC published with the original advisory. This vulnerability is fixed in 7.3.1.

Weakness: CWE-304 (Missing Critical Step in Authentication), CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-44547 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44547 is a critical authentication bypass vulnerability in ChurchCRM CRM, published on 12 May 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-44547 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-44547/ (Markdown: https://insights.sbomify.com/CVE-2026-44547/index.md)
```

## Sources

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

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