dbcve.org
ChurchcrmApplication

CVE-2023-38765

HIGH · 7.5 CVSS v3.1 Published 2023-08-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
SQL injection vulnerability in ChurchCRM v.5.0.0 allows a remote attacker to obtain sensitive information via the membermonth parameter within the /QueryView.php.

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

SQL injection vulnerability in ChurchCRM v5.0.0 allows remote attackers to inject malicious SQL queries through the 'membermonth' parameter in /QueryView.php, enabling unauthorized access to sensitive database information.

MitigationUpgrade to a patched version of ChurchCRM or implement parameterized queries/prepared statements for the membermonth parameter in QueryView.php to prevent SQL injection attacks.

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.0.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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Identify installed ChurchCRM version
    Locate the version file or check the dashboard/admin interface for the running ChurchCRM version number. Common locations include a version.php file, about page, or system information section in the admin panel.
    Affected if The installed version is exactly 5.0.0
  2. Locate QueryView.php file
    Search the web root directory for QueryView.php file. This file should exist in the web-accessible path of the ChurchCRM installation.
    Affected if QueryView.php file exists in the web directory and is accessible via HTTP/HTTPS
  3. Verify membermonth parameter handling
    Inspect the QueryView.php source code and search for any usage of the 'membermonth' parameter. Check if the parameter is directly used in SQL queries without proper sanitization or parameterized queries.
    Affected if The membermonth parameter is processed and used in SQL queries without prepared statements or input validation
  4. Check application database access
    Review the application's database configuration and verify if the database user configured for ChurchCRM has broad privileges (such as SELECT on sensitive tables).
    Affected if The database user has permissions that could allow an attacker to extract sensitive data through successful SQL injection

You are affected if running ChurchCRM version 5.0.0 with QueryView.php accessible and the membermonth parameter used in unsanitized SQL queries.

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 a patched version of ChurchCRM or implement parameterized queries/prepared statements for the membermonth parameter in QueryView.php to prevent SQL injection attacks.

Recommended fix Moderate confidence

5.0.1 or later stable release

  1. 1. Navigate to the ChurchCRM GitHub releases page (github.com/ChurchCRM/CRM/releases)
  2. 2. Look for a version newer than 5.0.0 that includes security fixes
  3. 3. Download the latest stable release (typically 5.0.1 or later)
  4. 4. Back up your existing ChurchCRM database and files
  5. 5. Replace the application files with the new version
  6. 6. Run any database migration scripts included in the upgrade
  7. 7. Verify the /QueryView.php endpoint no longer accepts unsanitized membermonth parameter
Caveat Review release notes for any database schema changes or configuration requirements before upgrading

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

Fix this in Churchcrm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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