dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-58411

HIGH · 7.0 CVSS v4.0 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 No privileges 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, Cross-Site Scripting (XSS) vulnerabilities were identified due to insufficient output encoding of user-controlled request parameter names and parameter values. The application reflects attacker-controlled input into JavaScript string contexts and HTML attribute contexts without proper sanitization or contextual output encoding. Affected endpoints observed during testing: /FamilyCustomFieldsEditor.php, /PaddleNumList.php and /admin/system/church-info. Potential consequences include session-token theft, account takeover, unauthorized actions on behalf of authenticated users, exposure of sensitive church member information, credential harvesting, phishing, and privilege escalation when administrators are targeted. This issue has been resolved 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 prior to 7.4.0 contain Reflected XSS vulnerabilities in multiple endpoints (/FamilyCustomFieldsEditor.php, /PaddleNumList.php, /admin/system/church-info) where user-controlled request parameter names and values are reflected into JavaScript string and HTML attribute contexts without proper output encoding or contextual sanitization, allowing injection of arbitrary script execution.

MitigationUpgrade to ChurchCRM version 7.4.0 or later, which implements proper output encoding; alternatively, apply contextual output encoding to all user-supplied input reflected into HTML/JavaScript contexts at the identified endpoints.

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
None
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:L/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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
    Locate the version file or check the admin interface (typically System Dashboard or /public/version.php) to determine the running version
    Affected if The installed version is any version prior to 7.4.0
  2. Verify affected endpoints exist
    Check if the following PHP files exist in the web root: FamilyCustomFieldsEditor.php, PaddleNumList.php, and the file handling /admin/system/church-info
    Affected if Any of these endpoint files are present and accessible on the server
  3. Test parameter reflection in FamilyCustomFieldsEditor.php
    Submit a crafted request with a test parameter (e.g., ?test=<script>alert(1)</script>) and inspect if the parameter name or value appears unencoded in the page response HTML or JavaScript
    Affected if User-supplied parameter names or values are reflected into the response without HTML encoding or JavaScript escaping
  4. Test parameter reflection in PaddleNumList.php
    Submit a crafted request with a test parameter and inspect the response for unencoded output in HTML attributes or JavaScript string contexts
    Affected if User-supplied parameter names or values are reflected into the response without HTML encoding or JavaScript escaping
  5. Test parameter reflection in admin/system/church-info
    Submit crafted parameters to the church-info endpoint and examine if input is reflected without contextual encoding in HTML or JavaScript contexts
    Affected if User-supplied parameter names or values are reflected into the response without HTML encoding or JavaScript escaping

The environment is affected if ChurchCRM version is below 7.4.0 AND any of the three vulnerable endpoints reflect user-controlled input without proper output encoding in HTML or JavaScript contexts.

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 implements proper output encoding; alternatively, apply contextual output encoding to all user-supplied input reflected into HTML/JavaScript contexts at the identified endpoints.

Recommended fix High confidence

ChurchCRM 7.4.0

  1. 1. Back up your current ChurchCRM installation and database
  2. 2. Download ChurchCRM version 7.4.0 or later from the official repository (github.com/ChurchCRM/CRM)
  3. 3. Extract the new version to your web server directory
  4. 4. Run any database migration scripts if included in the release
  5. 5. Verify the upgrade was successful by accessing the application
  6. 6. Test the previously vulnerable endpoints (/FamilyCustomFieldsEditor.php, /PaddleNumList.php, /admin/system/church-info) to confirm the XSS vulnerability is resolved

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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