CVE-2026-40480: CWE-639: Authorization Bypass Through User-Controlled Key in ChurchCRM CRM
ChurchCRM is an open-source church management system. In versions prior to 7.2.0, the GET /api/person/{personId} endpoint loads and returns person records without performing object-level authorization checks. Although the legacy PersonView.php page enforces canEditPerson() restrictions, the API layer omits this check. Any authenticated user with only EditSelf privileges can enumerate and read other members' records, exposing sensitive PII including names, addresses, phone numbers, and email addresses. This issue has been fixed in version 7.2.0.
AI Analysis
Technical Summary
The vulnerability in ChurchCRM CRM (CVE-2026-40480) arises because the API endpoint GET /api/person/{personId} does not enforce object-level authorization checks, unlike the legacy PersonView.php page which enforces canEditPerson() restrictions. This allows users with limited privileges (EditSelf) to bypass authorization controls and access other users' personal data. The flaw affects all versions prior to 7.2.0 and has been addressed in that release.
Potential Impact
Exploitation of this vulnerability enables unauthorized disclosure of sensitive personal information of other members, including names, addresses, phone numbers, and email addresses. This can lead to privacy violations and potential misuse of personal data. The CVSS 4.0 base score is 7.1, indicating a high severity impact due to network attack vector, low attack complexity, and no user interaction required.
Mitigation Recommendations
Upgrade ChurchCRM to version 7.2.0 or later, where this authorization bypass vulnerability has been fixed. Since the vendor advisory confirms the issue is resolved in 7.2.0, applying this official fix is the recommended remediation. No additional mitigation steps are indicated.
CVE-2026-40480: CWE-639: Authorization Bypass Through User-Controlled Key in ChurchCRM CRM
Description
ChurchCRM is an open-source church management system. In versions prior to 7.2.0, the GET /api/person/{personId} endpoint loads and returns person records without performing object-level authorization checks. Although the legacy PersonView.php page enforces canEditPerson() restrictions, the API layer omits this check. Any authenticated user with only EditSelf privileges can enumerate and read other members' records, exposing sensitive PII including names, addresses, phone numbers, and email addresses. This issue has been fixed in version 7.2.0.
CVSS v4.0
Score 7.1high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in ChurchCRM CRM (CVE-2026-40480) arises because the API endpoint GET /api/person/{personId} does not enforce object-level authorization checks, unlike the legacy PersonView.php page which enforces canEditPerson() restrictions. This allows users with limited privileges (EditSelf) to bypass authorization controls and access other users' personal data. The flaw affects all versions prior to 7.2.0 and has been addressed in that release.
Potential Impact
Exploitation of this vulnerability enables unauthorized disclosure of sensitive personal information of other members, including names, addresses, phone numbers, and email addresses. This can lead to privacy violations and potential misuse of personal data. The CVSS 4.0 base score is 7.1, indicating a high severity impact due to network attack vector, low attack complexity, and no user interaction required.
Mitigation Recommendations
Upgrade ChurchCRM to version 7.2.0 or later, where this authorization bypass vulnerability has been fixed. Since the vendor advisory confirms the issue is resolved in 7.2.0, applying this official fix is the recommended remediation. No additional mitigation steps are indicated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-13T19:50:42.114Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69e2c0dabdfbbecc599fc054
Added to database: 4/17/2026, 11:23:06 PM
Last enriched: 4/25/2026, 2:51:49 AM
Last updated: 6/1/2026, 10:13:20 PM
Views: 74
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.