CVE-2026-40582
Authentication Bypass in ChurchCRM API Grants Unauthorized Access
Publication date: 2026-04-18
Last updated on: 2026-04-18
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| churchcrm | churchcrm | to 7.2.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| CWE-288 | The product requires authentication, but the product has an alternate path or channel that does not require authentication. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
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.
How can this vulnerability impact me? :
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.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade ChurchCRM to version 7.2.0 or later, where the issue has been fixed.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
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.