/

CVE-2026-42289

Severity:

HIGH RISK

(8.8)

Improper Privilege Management (CWE-269) in ChurchCRM

CVE-2026-42289

Deferred

Vulnerability type

Category:

Improper Privilege Management

CWE:

CWE-269, CWE-306, CWE-352

Impact:

Unauthorized Account and Privilege Modification

Severity:

HIGH RISK

(8.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

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.

Sources

SourceLink
github.comgithub.com/ChurchCRM/CRM/security/advisories/GHSA-3xq9-c86x-cwpp

Frequently asked

questions

It may be exploitable through the ChurchCRM web interface when the affected

functionality is exposed and the relevant security checks are absent or

insufficient. The exact scope depends on deployment configuration and endpoint

access controls.

Not necessarily. CWE-306 is associated with missing authentication, but an

attacker may still need network access to the application. In deployments

that require login, a low-privilege account or a victim's browser session

could be relevant.

Enforce authentication, server-side authorization, and CSRF protection for

every account and permission operation. Apply least privilege and safe

defaults when assigning roles.

Centralize access-control decisions, test sensitive endpoints with multiple

privilege levels, protect all state-changing requests against CSRF, and

monitor audit logs for unexpected account or role changes.

Find out what's already
exploitable in your codebase.