Skip to content

Security: ChurchCRM/CRM

SECURITY.md

Security Policy

Stay Informed & Where to Ask

Security patch announcements, CVE disclosures, and dependency update notices are posted in the #security channel on our Discord server.

👉 Join Discord: https://discord.gg/w4mmYPSnE — then follow #security for announcements.

Please do not:

  • DM maintainers directly about security issues
  • Email individual maintainers or any role-specific address about security issues (no such contacts exist — use GitHub Security Advisories)
  • Post vulnerability details in any other Discord channel
  • Ask about undisclosed vulnerabilities in public channels

The #security channel is read-only for announcements. To report an issue, use the private GitHub Advisory process described below.


Reporting a Vulnerability vs. Filing a Bug

When to Use a Security Advisory (Private Disclosure)

Use GitHub's Security Advisory feature for issues that could be exploited by attackers, including:

  • Cross-Site Scripting (XSS) – Injection of malicious scripts
  • SQL Injection – Unauthorized database access
  • Authentication/Authorization Bypass – Accessing data without proper permissions
  • Session Hijacking – Stealing or manipulating user sessions
  • Remote Code Execution – Running arbitrary code on the server
  • Sensitive Data Exposure – Leaking passwords, personal information, or financial data
  • Cross-Site Request Forgery (CSRF) – Forcing users to perform unintended actions

Please do not open a public issue for security vulnerabilities. Public disclosure gives attackers time to exploit the issue before a fix is available.

When reporting a security vulnerability, include:

  • Description of the vulnerability and its potential impact
  • Steps to reproduce the vulnerability
  • Affected versions
  • Any relevant environment and configuration information
  • Proof of concept (if available)

We will acknowledge receipt within 1 week and provide updates on the fix timeline.

When to File a Regular Bug Report

Use GitHub Issues for general bugs that do not pose a security risk, such as:

  • UI/display issues or broken layouts
  • Features not working as expected
  • Error messages or crashes (without security implications)
  • Performance problems
  • Documentation errors
  • Installation or upgrade issues

If you're unsure whether an issue is security-related, err on the side of caution and use the Security Advisory.

Scope

The following activities are within the scope of our responsible disclosure process:

  • Reporting security vulnerabilities directly to us via GitHub Security Advisory
  • Providing steps to reproduce and validate the vulnerability
  • Sharing proof-of-concept code or test cases (privately, through the advisory)

Out of scope:

  • General bugs with no security impact — please use GitHub Issues instead
  • Feature requests or usability concerns — please use GitHub Issues instead
  • Vulnerabilities in self-hosted infrastructure outside of the ChurchCRM application and its bundled dependencies — please contact the affected site's administrator directly

Security Best Practices

ChurchCRM should only run on HTTPS connections. If you don't have an SSL certificate, Let's Encrypt provides free certificates.

No Security Testing on Demo Sites

For security and stability reasons, we kindly request that you do not perform any security testing on the demo sites provided by ChurchCRM. The demo sites are for showcasing purposes only, and any attempts to identify or exploit security vulnerabilities on these sites may lead to unintended disruptions.

If you are interested in security testing or assessments, please focus your efforts on your local development environments or any instances you have set up for testing purposes.

Thank you for your understanding and cooperation in making ChurchCRM a more secure platform.

Supported Versions

Only the latest release branch receives security fixes.

Version Supported PHP Version
7.1 + ✅ >=8.4
7.0.x ❌ >=8.3
6.0 - 6.x ❌ >=8.2
5.3 + ❌ >=8.1
5.0 - 5.2.x ❌ 8.1
4.0.x ❌ 7.2.x 7.3.x
3.0.x ❌ 7.x
2.0.x ❌ 5.6 7.0 7.1

Severity Assessment: Admin-Only Vulnerabilities

When assessing vulnerability severity, we consider the practical risk posed by the issue, not just its technical exploitability.

Admin-only vulnerabilities are marked as Low severity when:

  • The vulnerability can only be exploited by authenticated administrators
  • Administrators already have broad system access (database modification, data export, settings access)
  • The attack requires intentional abuse by a trusted insider, not external compromise

Rationale: An admin with malicious intent can already cause significant harm through normal system access (e.g., modifying database records, exporting all data, changing settings). A vulnerability that only admins can exploit adds no new external attack surface — it only affects insider risk, which is outside the scope of a public security advisory.

Examples:

  • CSRF on admin-only fundraiser functions (admin can already modify fundraiser data)
  • IDOR in admin-only editors (admin can already view/edit any record)
  • Session-fixation on admin login (admin already has system access)

Not marked Low:

  • Vulnerabilities accessible to non-admin users
  • Privilege escalation from user → admin
  • Vulnerabilities affecting public-facing features

Developer Security

For developers contributing to ChurchCRM, see the Developer Security Guide, which covers security best practices including Content Security Policy (CSP) compliance.

Learn more about advisories related to ChurchCRM/CRM in the GitHub Advisory Database