ChurchCRM up to 7.1.x API Endpoint /api/public/user/login authentication bypass

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.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-23601). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• ChurchCRM

Version

• 7.0
• 7.1

License

• open-source

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion