ChurchCRM Auth Bypass (CVE-2026-39339)
CVE-2026-39339
ChurchCRM is an open-source church management system. Prior to 7.1.0, a critical authentication bypass vulnerability in ChurchCRM's API middleware (ChurchCRM/Slim/Middleware/AuthMiddleware.php) allow...
Overview
A critical security flaw in ChurchCRM allows unauthenticated attackers to bypass authentication entirely and access sensitive data. The vulnerability, tracked as CVE-2026-39339, exists in versions prior to 7.1.0 and has a CVSS score of 9.1.
Vulnerability Details
The flaw resides in the API authentication middleware (AuthMiddleware.php). The middleware incorrectly validates request URLs. If the string “api/public” appears anywhere in the request URL path, the middleware incorrectly treats the entire request as a public call, skipping all authentication checks. This allows any attacker to directly query protected API endpoints without providing valid credentials.
Impact
The impact of this vulnerability is severe. Attackers can access every protected API endpoint, which typically includes:
- Complete church member directories (names, addresses, contact details).
- Financial contribution records and other sensitive pastoral data.
- System configuration information. This constitutes a total compromise of the application’s data security, leading to a significant privacy breach for the congregation. For more on the consequences of such exposures, see our breach reports.
Remediation and Mitigation
The only complete remediation is to immediately upgrade ChurchCRM to version 7.1.0 or later, which contains the fix. Action Steps:
- Update Immediately: All instances running a version below 7.1.0 must be upgraded to the patched release.
- Audit Access Logs: Review web server and application logs for suspicious requests containing “api/public” from unauthorized IP addresses.
- Assume Compromise: Given the ease of exploitation, organizations should assume member data may have been accessed and follow relevant data breach notification procedures.
If an immediate upgrade is not possible, as a temporary and incomplete mitigation, consider restricting network access to the ChurchCRM application to known trusted networks only. However, this does not fix the underlying vulnerability.
Security Insight
This vulnerability highlights the danger of flawed path-matching logic in security middleware, a recurring theme in web application flaws. Similar to past incidents in other platforms, a single logic error in a central authentication component can nullify the entire security model. It underscores the critical need for rigorous, negative-testing of security controls-ensuring they fail securely rather than granting excessive access. For ongoing coverage of similar threats, follow our security news.
Further Reading
Never miss a critical vulnerability
Get real-time security alerts delivered to your preferred platform.
Related Advisories
The goodoneuz/pay-uz Laravel package (<= 2.2.24) contains a critical vulnerability in the /payment/api/editable/update endpoint that allows unauthenticated attackers to overwrite existing PHP payment ...
Reviactyl is an open-source game server management panel built using Laravel, React, FilamentPHP, Vite, and Go. From version 26.2.0-beta.1 to before version 26.2.0-beta.5, a vulnerability in the OAuth...
Vulnerability in the Oracle Edge Cloud Infrastructure Designer and Visualisation Toolkit product of Oracle Open Source Projects (component: Desktop). The supported version that is affected is 0.3.0....
Winter is a free, open-source content management system (CMS) based on the Laravel PHP framework. Prior to 1.0.477, 1.1.12, and 1.2.12, Winter CMS allowed authenticated backend users to escalate their...