Is CVE-2026-44547 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-44547 being exploited in the wild.

How severe is CVE-2026-44547?

Critical severity, with a CVSS score of 9.6, published 12 May 2026.

Is there a fix for CVE-2026-44547?

A patch was published on 2026-04-29: Fix merged into master for version 7.3.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-44547 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-44547?

Check whether you run ChurchCRM at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-44547: ChurchCRM 2FA and account lockout bypass in public API login

CVE-2026-44547 · Severity: critical · CVSS 9.6 · Published 2026-05-12

ChurchCRM, an open-source church management system, is affected by a security flaw where the public login interface for its API fails to enforce two-factor authentication (2FA) and account lockout protections. This occurred because a previous security fix was accidentally removed during the software development process. An attacker with a user's password can bypass 2FA requirements to gain full access to sensitive financial and member data, even if the account was supposed to be locked due to suspicious activity.

Technologies: ChurchCRM. Vendors: ChurchCRM.

Quick answers

Is CVE-2026-44547 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-44547 being exploited in the wild.
How severe is CVE-2026-44547?: Critical severity, with a CVSS score of 9.6, published 12 May 2026.
Which products and versions are affected?: ChurchCRM 7.2.0 - 7.2.2.
Is there a fix for CVE-2026-44547?: A patch was published on 2026-04-29: Fix merged into master for version 7.3.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-44547 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-44547?: Check whether you run ChurchCRM at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A regression in ChurchCRM versions 7.2.0 through 7.2.2 caused the silent removal of security hardening logic in 'src/api/routes/public/public-user.php'. Specifically, the 'userLogin' function lacks calls to 'isLocked()', 'setFailedLogins()', and 'is2FactorAuthEnabled()'. While the web-based browser login correctly enforces these controls, the public API endpoint returns a valid 'apiKey' upon password validation alone. An attacker with valid user credentials can bypass 2FA and account lockouts to obtain an API key, which can then be used to access protected routes (such as financial deposits) via 'AuthMiddleware.php'. This is an incomplete fix for a previous vulnerability (CVE-2026-40582). The issue is resolved in version 7.3.1.

Affected products

ChurchCRM ChurchCRM 7.2.0 - 7.2.2

Timeline

2026-04-29: patched: Fix merged into master for version 7.3.1
2026-05-01: advisory: GitHub Security Advisory GHSA-cwp8-rm8g-q5c9 published
2026-05-12: disclosed: CVE-2026-44547 published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.