CVE-2026-58408
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 · uneditedChurchCRM is an open-source church management system. Prior to version 7.4.0, a low-privileged user can bypass the /admin/export UI and exfiltrate the entire member directory. The POST /CSVCreateFile.php endpoint generates and streams a CSV containing the full Personally Identifiable Information (PII) of every Person/Family record in the database, without performing any feature-level or object-level authorization check beyond the coarse "has any admin permission" gate inherited from the legacy page bootstrap. In other words, any single non-admin permission flag is enough to reach the CSV bulk-export endpoint, even though such users should not have data export rights. The export script is missing a dedicated isAdmin() (or a new bExportData) authorization check of its own. 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 confidenceThe /CSVCreateFile.php endpoint in ChurchCRM versions prior to 7.4.0 lacks proper authorization checks for data export functionality. The endpoint only verifies that a user possesses any admin permission flag, allowing any low-privileged user with minimal admin access to generate and download a CSV containing the complete PII database (all Person/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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify ChurchCRM installation and versionLocate the ChurchCRM web application directory and check the version identifier (typically in a version.php file, composer.json, or the application header). Compare the installed version number to the affected range (versions prior to 7.4.0).Affected if The installed version is lower than 7.4.0
-
Verify the vulnerable endpoint existsCheck for the presence of /CSVCreateFile.php in the web-accessible directory (commonly in the root or /include directory of the ChurchCRM installation).Affected if The file CSVCreateFile.php exists in the web application path
-
Inspect endpoint authorization logicOpen CSVCreateFile.php and examine the permission check logic. Look for how the script verifies user authorization - specifically whether it calls only a generic isAdmin() or checks for any admin permission flag, versus a specific bExportData permission check.Affected if The endpoint only verifies the user has any admin permission (isAdmin() or equivalent) without specifically checking for bExportData permission
A user is affected if running a ChurchCRM version below 7.4.0 where the CSVCreateFile.php endpoint uses only generic admin permission checks instead of requiring explicit bExportData authorization.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to ChurchCRM version 7.4.0, which implements proper feature-level authorization (isAdmin() or bExportData permission check) for the CSV export endpoint.
7.4.0
- 1. Backup the current ChurchCRM database and files before attempting any upgrade.
- 2. Download ChurchCRM version 7.4.0 from the official GitHub repository (github.com/ChurchCRM/CRM) or the releases page.
- 3. Replace the existing ChurchCRM installation files with the new version 7.4.0 files, preserving configuration files and any custom assets.
- 4. Run the database upgrade scripts included in version 7.4.0 if any are present.
- 5. Verify the upgrade was successful by logging in and checking the version number in the system.
- 6. Confirm the /CSVCreateFile.php endpoint now properly enforces authorization by testing with a low-privileged non-admin account.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-58408 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-58408 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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