CVE-2026-40582: CWE-288: Authentication Bypass Using an Alternate Path or Channel in ChurchCRM CRM
ChurchCRM versions prior to 7. 2. 0 contain an authentication bypass vulnerability in the /api/public/user/login endpoint. This endpoint validates only username and password before returning the user's API key, bypassing account lockout and two-factor authentication protections. An attacker who knows a user's password can gain API access with that user's privileges even if the account is locked or 2FA is enabled. The issue has been fixed in version 7. 2. 0. No known exploits are reported in the wild.
AI Analysis
Technical Summary
CVE-2026-40582 is an authentication bypass vulnerability in ChurchCRM CRM versions before 7.2.0. The vulnerability exists because the /api/public/user/login endpoint returns the user's API key after validating only username and password, circumventing the normal authentication flow that enforces account lockout and two-factor authentication. This allows an attacker with knowledge of a user's password to obtain API access and interact with all protected API endpoints with that user's privileges, regardless of account lockout status or 2FA enforcement. The vulnerability is classified under CWE-288 (Authentication Bypass Using Alternate Path or Channel) and CWE-305 (Authentication Bypass by Primary Weakness). The issue was resolved in ChurchCRM version 7.2.0.
Potential Impact
An attacker who knows a valid user's password can bypass account lockout and two-factor authentication protections to obtain the user's API key. This grants the attacker direct access to all API endpoints accessible by that user, potentially exposing sensitive data or allowing unauthorized actions within the ChurchCRM system. The vulnerability is rated critical with a CVSS 4.0 score of 9.1, indicating high impact on confidentiality and integrity with network attack vector and no user interaction required. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrade ChurchCRM to version 7.2.0 or later, where this vulnerability has been fixed. Until the upgrade is applied, be aware that accounts with locked status or two-factor authentication enabled can still be bypassed via the vulnerable API endpoint if an attacker knows the user's password. No other mitigations are specified in the vendor advisory or CVE data.
CVE-2026-40582: CWE-288: Authentication Bypass Using an Alternate Path or Channel in ChurchCRM CRM
Description
ChurchCRM versions prior to 7. 2. 0 contain an authentication bypass vulnerability in the /api/public/user/login endpoint. This endpoint validates only username and password before returning the user's API key, bypassing account lockout and two-factor authentication protections. An attacker who knows a user's password can gain API access with that user's privileges even if the account is locked or 2FA is enabled. The issue has been fixed in version 7. 2. 0. No known exploits are reported in the wild.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-40582 is an authentication bypass vulnerability in ChurchCRM CRM versions before 7.2.0. The vulnerability exists because the /api/public/user/login endpoint returns the user's API key after validating only username and password, circumventing the normal authentication flow that enforces account lockout and two-factor authentication. This allows an attacker with knowledge of a user's password to obtain API access and interact with all protected API endpoints with that user's privileges, regardless of account lockout status or 2FA enforcement. The vulnerability is classified under CWE-288 (Authentication Bypass Using Alternate Path or Channel) and CWE-305 (Authentication Bypass by Primary Weakness). The issue was resolved in ChurchCRM version 7.2.0.
Potential Impact
An attacker who knows a valid user's password can bypass account lockout and two-factor authentication protections to obtain the user's API key. This grants the attacker direct access to all API endpoints accessible by that user, potentially exposing sensitive data or allowing unauthorized actions within the ChurchCRM system. The vulnerability is rated critical with a CVSS 4.0 score of 9.1, indicating high impact on confidentiality and integrity with network attack vector and no user interaction required. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrade ChurchCRM to version 7.2.0 or later, where this vulnerability has been fixed. Until the upgrade is applied, be aware that accounts with locked status or two-factor authentication enabled can still be bypassed via the vulnerable API endpoint if an attacker knows the user's password. No other mitigations are specified in the vendor advisory or CVE data.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-14T13:24:29.475Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69e2c0dabdfbbecc599fc05f
Added to database: 4/17/2026, 11:23:06 PM
Last enriched: 4/17/2026, 11:38:04 PM
Last updated: 4/18/2026, 6:47:50 AM
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.