dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-58409

CRITICAL · 9.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 →
97/100
Remediation priority · Urgent
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, an authenticated administrator can achieve Remote Code Execution (RCE) on the server by installing a malicious plugin ZIP archive containing a PHP webshell. The application explicitly includes 'php' in its ALLOWED_EXTENSIONS list, while the dangerous extensions denylist (DENIED_EXTENSIONS) fails to block standard .php files. Because `php` is explicitly included in the allowed extension list for plugin archives, and extracted files are placed directly under the web root, any PHP file inside the ZIP becomes immediately executable via HTTP — without even needing to "enable" the plugin through the application UI. The /plugins/install-url API route (management.php) allows an administrator to source the malicious ZIP from any attacker-controlled HTTPS URL, validating it only against an attacker-supplied SHA-256 hash. 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 allow authenticated administrators to achieve RCE by uploading malicious plugin ZIP archives. The application explicitly includes 'php' in ALLOWED_EXTENSIONS while the denylist fails to block .php files, and extracted files are placed directly under the web root, making any PHP file immediately executable via HTTP. The /plugins/install-url API validates only against an attacker-supplied SHA-256 hash.

MitigationUpgrade to ChurchCRM version 7.4.0 or later, which fixes the extension validation logic and prevents execution of uploaded PHP files.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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. Check ChurchCRM version
    Locate the version file or admin dashboard version display (typically in /Include/Config.php or the About page). Compare the installed version to 7.4.0.
    Affected if Installed version is earlier than 7.4.0
  2. Verify plugin installation endpoint accessibility
    Attempt to access the /plugins/install-url API endpoint or check if the plugin upload/installation feature is exposed in the admin interface.
    Affected if The plugin installation feature is accessible to administrator accounts
  3. Inspect ALLOWED_EXTENSIONS configuration
    Review the application configuration files (typically in /Include/Config.php or similar) for the ALLOWED_EXTENSIONS setting used during plugin ZIP extraction.
    Affected if ALLOWED_EXTENSIONS includes 'php' or '.php'
  4. Inspect DENIED_EXTENSIONS configuration
    Review the same configuration files for the DENIED_EXTENSIONS setting to verify whether .php files are explicitly blocked.
    Affected if DENIED_EXTENSIONS is missing '.php' or 'php' from its blocklist, or is not defined
  5. Check web root for unactivated plugin files
    Examine the web document root directory structure. Look for any PHP files in the /plugins/ or root directories that were extracted from ZIP archives but not formally activated through the plugin system.
    Affected if Unsigned or unactivated PHP files exist in the web-accessible directory structure

An environment is affected if it runs ChurchCRM before version 7.4.0, has the plugin installation feature enabled, allows PHP extensions in uploads, and has unauthenticated or low-privilege access to the web root where extracted PHP files can be executed.

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 to ChurchCRM version 7.4.0 or later, which fixes the extension validation logic and prevents execution of uploaded PHP files.

Recommended fix High confidence

ChurchCRM version 7.4.0

  1. Upgrade ChurchCRM to version 7.4.0 or later to remediate this vulnerability
  2. If immediate upgrade is not possible, disable or restrict the plugin installation functionality (/plugins/install-url API route) for administrators until the upgrade can be performed
  3. Review administrator accounts and API access to ensure no compromised credentials are being used

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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