Riskcovery

CVE-2026-40582

ChurchCRM: Authentication Bypass in `/api/public/user/login` Allows Bypass of 2FA and Account Lockout

State
Published
Severity
9.1 Critical
Published
Apr 17, 2026
Updated
Apr 20, 2026
Reserved
Apr 14, 2026

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
4.09.1 CriticalCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NGitHub_M

Weaknesses

  • CWE-288 Authentication Bypass Using an Alternate Path or Channel
  • CWE-305 Authentication Bypass by Primary Weakness

Affected Products

ProductVersions
CRMChurchCRM
  • < 7.2.0Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.