Summary
ChurchCRM versions prior to 7.2.0 expose a family record deletion endpoint that performs irreversible deletion of families and all associated data via a simple GET request without CSRF protection.
An attacker can lure an authenticated administrator to a crafted web page that silently issues deletion requests, resulting in unintended loss of notes, pledges, person records, and property data without any explicit confirmation or interaction.
Affected context
The vulnerability occurs in the ChurchCRM family record deletion workflow, specifically in the SelectDelete.php endpoint responsible for permanent family removal.
It is relevant in deployments where:
- Administrators manage family records through a browser session
- The application exposes state-changing operations (like delete) over plain GET requests
- CSRF tokens or equivalent request-origin checks are not enforced for destructive actions
Under these conditions, a browser visiting an attacker-controlled page can unknowingly issue valid deletion requests while still authenticated to ChurchCRM.
Exploit preconditions
- Attack surface: Web application endpoint
SelectDelete.phpaccepting GET requests to delete families - Required access: Attacker does not need direct ChurchCRM access, but the victim must be an authenticated administrator with permission to delete families
- Trigger point: Victim visits an attacker-controlled page (or embedded resource) while logged into ChurchCRM, causing the browser to auto-send the crafted GET request
- Why exploitation is possible:
- The deletion action is mapped to a simple, side-effecting GET request
- No CSRF token or origin validation is required for the request
- The browser automatically includes the victim's session cookies, making the request appear legitimate to the server
Why this happens
The core issue is a missing CSRF defense on a high-impact, state-altering operation, combined with the misuse of HTTP GET for a destructive action.
This maps to CWE-352: Cross-Site Request Forgery (CSRF), where the application trusts any request bearing valid authentication cookies without verifying user intent or request origin.
Additionally, the absence of robust authorization checks per action (CWE-862) can exacerbate the risk if role-based verification on delete operations is weak or inconsistently enforced.
At an abstract level, the pattern is: "browser-authenticated state changes are performed solely based on session cookies, without any user-specific, non-replayable confirmation token, and are exposed via idempotent-looking endpoints."
Potential impact
- Irreversible deletion of family records without the administrator's knowledge
- Loss of associated notes, pledges, person records, and property data
- Integrity corruption of membership and financial records
- Operational disruption for organizations relying on ChurchCRM data for day-to-day activities
- Potential compliance or audit issues due to missing or incomplete historical records
General mitigation guidance
Mitigations generally focus on enforcing strong CSRF protections and aligning HTTP semantics with security expectations.
Recommended defensive patterns include:
- Requiring cryptographically strong, per-session or per-request CSRF tokens on all state-changing operations, especially destructive ones
- Restricting deletion and similar critical actions to POST (or other non-GET methods) and validating content type and origin where feasible
- Introducing explicit user confirmation steps (e.g., confirmation pages or dialogs) for irreversible deletions
- Ensuring fine-grained authorization checks on each sensitive operation so only appropriately privileged roles can trigger them
- Applying defense-in-depth measures such as SameSite cookies and origin/referrer checks to make cross-site triggering harder
Designing destructive endpoints to be "hard to call accidentally" and "hard to call cross-site" significantly reduces the attack surface.
How teams detect issues like this
Effective detection centers on identifying unprotected, state-changing endpoints and validating that CSRF controls are consistently applied.
Possible approaches:
- Static analysis rules that flag:
- State-changing operations (e.g., delete/update actions) exposed over HTTP GET
- Form handlers or controllers that modify server-side state without checking a CSRF token or similar nonce
- Code review checklists that explicitly require:
- Verification of CSRF defenses on all create/update/delete endpoints
- Confirmation that HTTP methods align with REST and security best practices
- Automated tests or security scanners that:
- Attempt cross-origin requests to known sensitive endpoints and verify whether they are accepted without anti-CSRF tokens
- Configuration and policy enforcement in CI/CD pipelines to prevent merging of new endpoints lacking documented CSRF handling

