dbcve.org
ChurchcrmApplication

CVE-2025-11529

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-09
Fix available
A fix is available. Upgrade to 5.19.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A security flaw has been discovered in ChurchCRM up to 5.18.0. This impacts the function AuthMiddleware of the file src/ChurchCRM/Slim/Middleware/AuthMiddleware.php of the component API Endpoint. The manipulation results in missing authentication. The attack can be executed remotely. The exploit has been released to the public and may be used for attacks. The patch is identified as 3a1cffd2aea63d884025949cfbcfd274d06216a4. A patch should be applied to remediate this issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

ChurchCRM versions up to 5.18.0 contain a missing authentication vulnerability in the AuthMiddleware function within the API endpoint component (src/ChurchCRM/Slim/Middleware/AuthMiddleware.php). The vulnerability allows unauthenticated remote attackers to bypass authentication checks and access protected API endpoints.

MitigationApply the provided patch (commit 3a1cffd2aea63d884025949cfbcfd274d06216a4) to remediate the AuthMiddleware, or upgrade to version 5.18.1 or later which includes the fix.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChurchcrmApplication
Affected:< 5.19.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed ChurchCRM version
    Check the version file or dashboard about page: look for version.php, composer.json, or the admin interface version display
    Affected if The installed version is less than 5.19.0 (any version from 5.0.0 through 5.18.0 is vulnerable)
  2. Locate the AuthMiddleware.php file
    Search for the file at src/ChurchCRM/Slim/Middleware/AuthMiddleware.php in the ChurchCRM installation directory
    Affected if The file exists in the installation, indicating the vulnerable component is present
  3. Inspect the AuthMiddleware implementation
    Open AuthMiddleware.php and examine the middleware function that handles authentication checks for API routes
    Affected if The middleware contains logic that fails to properly enforce authentication, allowing unauthenticated requests to pass through
  4. Verify API endpoint exposure
    Test accessing a known protected API endpoint (such as /api/users or /api/families) without providing valid authentication credentials
    Affected if The API endpoint returns successful data or a non-401 response without authentication tokens
  5. Check for the patched version file
    Look for version indicators in the codebase that may show if patch commit 3a1cffd2aea63d884025949cfbcfd274d06216a4 was applied, or examine the AuthMiddleware for the fix
    Affected if The code shows no evidence of the authentication fix being applied

A user is affected if their ChurchCRM installation is any version below 5.19.0 and the API endpoints are accessible without authentication credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.19.0 or later
Fixed in 5.19.0
Vendor patch github.com →
Interim mitigation

Apply the provided patch (commit 3a1cffd2aea63d884025949cfbcfd274d06216a4) to remediate the AuthMiddleware, or upgrade to version 5.18.1 or later which includes the fix.

Recommended fix High confidence

ChurchCRM 5.19.0

  1. Backup your ChurchCRM database and files before upgrading
  2. Download ChurchCRM version 5.19.0 from the official releases (https://github.com/ChurchCRM/CRM/releases)
  3. Extract the new version and replace the existing installation files, or use your preferred upgrade method
  4. Run any database migrations if required by the upgrade
  5. Verify the AuthMiddleware.php file contains the patch from commit 3a1cffd2aea63d884025949cfbcfd274d06216a4
  6. Test that authentication is now properly enforced on API endpoints

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Churchcrm Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11529 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11529 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data