CVE-2026-40582
Received Received - Intake
Authentication Bypass in ChurchCRM API Grants Unauthorized Access

Publication date: 2026-04-18

Last updated on: 2026-04-18

Assigner: GitHub, Inc.

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-18
Last Modified
2026-04-18
Generated
2026-06-16
AI Q&A
2026-04-18
EPSS Evaluated
2026-06-15
NVD
CVE-2026-40582
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
churchcrm churchcrm to 7.2.0 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-288 The product requires authentication, but the product has an alternate path or channel that does not require authentication.
CWE-305 The authentication algorithm is sound, but the implemented mechanism can be bypassed as the result of a separate weakness that is primary to the authentication error.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability exists in ChurchCRM versions prior to 7.2.0 in the /api/public/user/login endpoint. The endpoint only validates the username and password before returning the user's API key, bypassing the usual authentication steps such as account lockout and two-factor authentication (2FA).

As a result, an attacker who knows a user's password can obtain API access even if the account is locked or 2FA is enabled, allowing them to access all protected API endpoints with that user's privileges.

This issue was fixed in version 7.2.0.

Impact Analysis

If exploited, this vulnerability allows an attacker to bypass important security controls such as account lockout and two-factor authentication.

An attacker with knowledge of a user's password can gain unauthorized API access with that user's privileges, potentially accessing or manipulating sensitive data and functions within the ChurchCRM system.

This could lead to data breaches, unauthorized actions, and compromise of the integrity and confidentiality of the system.

Mitigation Strategies

To mitigate this vulnerability, upgrade ChurchCRM to version 7.2.0 or later, where the issue has been fixed.

Compliance Impact

This vulnerability allows an attacker who knows a user's password to bypass account lockout and two-factor authentication protections, gaining unauthorized API access with the user's privileges.

Such unauthorized access could lead to exposure or misuse of sensitive personal or health information managed by the system, potentially violating data protection requirements under standards like GDPR and HIPAA.

Therefore, the vulnerability undermines security controls that are critical for compliance with these regulations, increasing the risk of data breaches and non-compliance.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-40582. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart