CVE-2026-40582 | ChurchCRM up to 7.1.x API Endpoint /api/public/user/login authentication bypass (GHSA-8cwr-x83m-mh9x)

VDB-358173 · CVE-2026-40582 · GHSA-8CWR-X83M-MH9X CHURCHCRM UP TO 7.1.X API ENDPOINT /API/PUBLIC/USER/LOGIN AUTHENTICATION BYPASS HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 7.0 $0-$5k 0.00+ Summaryinfo A vulnerability marked as critical has been reported in ChurchCRM up to 7.1.x. This affects an unknown part of the file /api/public/user/login of the component API Endpoint. Performing a manipulation results in authentication bypass. This vulnerability was named CVE-2026-40582. The attack may be initiated remotely. There is no available exploit. It is suggested to upgrade the affected component. Detailsinfo A vulnerability classified as critical has been found in ChurchCRM up to 7.1.x. This affects an unknown code of the file /api/public/user/login of the component API Endpoint. The manipulation with an unknown input leads to a authentication bypass vulnerability. CWE is classifying the issue as CWE-288. A product requires authentication, but the product has an alternate path or channel that does not require authentication. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is: 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. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-40582 since 04/14/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. Upgrading to version 7.2.0 eliminates this vulnerability. Applying the patch 214694eb83778e1f5e52b3dfa2a99d0e965c1850 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. Productinfo Name ChurchCRM Version 7.0 7.1 License open-source CPE 2.3info 🔒 🔒 CPE 2.2info 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 7.3 VulDB Meta Temp Score: 7.0 VulDB Base Score: 7.3 VulDB Temp Score: 7.0 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Authentication bypass CWE: CWE-288 / CWE-287 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: ChurchCRM 7.2.0 Patch: 214694eb83778e1f5e52b3dfa2a99d0e965c1850 Timelineinfo 04/14/2026 CVE reserved 04/18/2026 +4 days Advisory disclosed 04/18/2026 +0 days VulDB entry created 04/18/2026 +0 days VulDB entry last update Sourcesinfo Advisory: GHSA-8cwr-x83m-mh9x Status: Confirmed CVE: CVE-2026-40582 (🔒) GCVE (CVE): GCVE-0-2026-40582 GCVE (VulDB): GCVE-100-358173 Entryinfo Created: 04/18/2026 09:17 Changes: 04/18/2026 09:17 (70) Complete: 🔍 Cache ID: 99:7DD:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸