Summary
ChurchCRM versions before 7.3.2 contain an access-control weakness in UserEditor.php, which handles user creation and permission updates. If the relevant operations are reachable without sufficient authentication, authorization, or request-integrity checks, an attacker may create accounts or alter privileges.
Affected context
The issue occurs in ChurchCRM deployments where UserEditor.php processes account and permission changes without consistently enforcing authentication, authorization, and anti-forgery protections. Risk depends on endpoint exposure, configured roles, session controls, and whether requests can be issued by unauthorized users or induced through another user's browser.
Exploit preconditions
- Attack surface: The web-accessible user-management functionality in
UserEditor.php - Required access: Potentially unauthenticated or low-privilege web access, depending on deployment and request handling
- Trigger point: User account creation or permission-update requests
- Why exploitation is possible: Missing or incomplete authentication, authorization, and request-integrity checks may allow sensitive administrative actions to be processed outside the intended privilege boundary
Why this happens
The underlying bug class is improper privilege management: sensitive account and permission operations are not reliably bound to an authenticated identity with the required administrative authority. Related weaknesses include missing authentication checks (CWE-306) and cross-site request forgery exposure (CWE-352), where state-changing requests may be accepted without sufficiently proving the request's origin and user intent.
Potential impact
- An attacker may create unauthorized user accounts.
- An attacker could assign elevated permissions to an existing or newly created account.
- Unauthorized changes may compromise sensitive ChurchCRM data.
- The application may experience loss of administrative control.
- A successful attack can enable further actions available to the granted role.
General mitigation guidance
Mitigation generally focuses on enforcing authorization at every sensitive
server-side operation rather than relying on interface visibility.
Common defensive patterns include:
- Require authentication before processing account or permission changes.
- Apply explicit server-side role and ownership checks for each operation.
- Use secure-by-default permission assignments for newly created accounts.
- Require anti-CSRF tokens and appropriate same-site cookie protections for state-changing requests.
- Validate submitted identifiers and requested roles against an allowlist.
- Separate user creation from privilege administration and restrict both by least privilege.
- Record and alert on unexpected account creation or privilege changes.
How teams detect issues like this
Organizations can assess this class of issue through:
- Static analysis for sensitive handlers lacking authentication or authorization guards.
- Code review checks for direct updates to users, roles, or permissions from request parameters.
- Tests that exercise account and privilege operations as unauthenticated and low-privilege users.
- Cross-site request forgery testing for state-changing forms and endpoints.
- Policy enforcement requiring centralized access-control checks for administrative actions.
- Audit-log monitoring for unusual account creation, role changes, or privilege escalation.

