dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-58410

HIGH · 7.1 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click 5 weeks old

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
ChurchCRM is an open-source church management system. Prior to version 7.4.0, there was an authorization flaw in the family-scoped endpoints which allowed low-privileged users to read and modify other families’ records. An authenticated non-admin user with EditSelf access can supply another family’s `familyId` and access records outside their own family scope. The backend trusts the attacker-controlled `familyId` and loads the corresponding family entity by ID without verifying that the requested family belongs to the current user. If the same user also has Notes permission, they can create notes on another family’s record. This breaks the intended EditSelf scope and allows access to unrelated congregation records. This issue has been fixed in version 7.4.0.

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 before 7.4.0 contain an Insecure Direct Object Reference (IDOR) vulnerability where authenticated users with EditSelf permission can access other families' records by manipulating the familyId parameter in family-scoped API endpoints. The backend loads the family entity by ID without verifying that the requested family belongs to the current user, allowing unauthorized cross-family data access and modification.

MitigationUpgrade ChurchCRM to version 7.4.0 or later. Additionally, audit all family-scoped endpoints to ensure proper ownership validation is performed before returning or modifying any family records.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

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

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 information stored in the application configuration file (typically includes a version.php, config.php, or similar) or query the database for version metadata.
    Affected if The installed version is lower than 7.4.0 (e.g., 7.3.x, 7.2.x, earlier releases).
  2. Locate users with EditSelf permission
    Query the user permission database table or inspect the user management interface to identify accounts that have the EditSelf permission enabled.
    Affected if Any user account has EditSelf permission granted, which permits the user to edit their own profile and potentially trigger the vulnerable code path.
  3. Verify family-scoped API endpoint accessibility
    Identify API endpoints that accept a familyId parameter (commonly found in routes like /api/family/{familyId}, /api/families/{id}, or similar family-related endpoints). Test accessing these endpoints with a valid authenticated session that has EditSelf permissions.
    Affected if The API accepts and processes requests containing arbitrary familyId values without additional ownership verification.
  4. Confirm missing ownership validation in backend code
    Inspect the server-side code handling family-scoped API requests (look for controller or service files that process familyId parameters). Verify whether the code checks if the current user's family matches the requested familyId before returning data.
    Affected if The backend code loads family records by ID without validating that the currently authenticated user is associated with (owns) that family record.

A user is affected if running ChurchCRM version below 7.4.0 with EditSelf permission enabled, and the family-scoped API endpoints lack ownership verification to prevent cross-family access.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade ChurchCRM to version 7.4.0 or later. Additionally, audit all family-scoped endpoints to ensure proper ownership validation is performed before returning or modifying any family records.

Recommended fix High confidence

7.4.0

  1. Backup the ChurchCRM database before any upgrade
  2. Confirm current ChurchCRM version is below 7.4.0
  3. Upgrade ChurchCRM to version 7.4.0 using the standard upgrade process for your deployment method
  4. Verify the upgrade was successful by logging in and confirming the application functions normally
  5. Test that the family-scoped endpoints now properly enforce authorization checks

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-58410 — 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-2026-58410 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