dbcve.org
ChurchcrmApplication

CVE-2023-38768

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 PropertyID 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 unauthenticated remote attackers to inject malicious SQL queries via the PropertyID parameter in /QueryView.php, potentially exposing sensitive database contents including user credentials, personal information, and other application data.

MitigationImplement parameterized queries or prepared statements in QueryView.php to safely handle the PropertyID parameter, or update to a patched version if available. Input validation and proper escaping should also be applied as defense-in-depth.

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 ChurchCRM installation directory and check the version file or header. Common locations include a version.php file or the system dashboard that displays the software version.
    Affected if The installed version is exactly 5.0.0 (matching the affected version range). Earlier versions or patched versions may not be affected.
  2. Verify QueryView.php exists
    Locate the QueryView.php file within the ChurchCRM web root directory. This file is required for the SQL injection to be exploitable.
    Affected if QueryView.php exists in the web-accessible directory, indicating the potentially vulnerable component is present.
  3. Examine PropertyID parameter handling in QueryView.php
    Open QueryView.php and search for code that handles the 'PropertyID' parameter. Look for direct inclusion of this parameter in SQL queries without using prepared statements or parameter binding.
    Affected if The code constructs SQL queries by directly concatenating or interpolating the PropertyID parameter into the query string without parameterized queries.
  4. Check if QueryView is accessible without authentication
    Attempt to access the QueryView.php endpoint directly via HTTP without providing authentication credentials. Determine if the endpoint permits unauthenticated access.
    Affected if The endpoint responds to unauthenticated requests, meaning the SQL injection is reachable without prior authentication.
  5. Review web server logs for suspicious PropertyID values
    Examine access logs for requests to QueryView.php containing unusual characters in the PropertyID parameter (such as quotes, UNION, SELECT, or SQL keywords) that may indicate exploitation attempts.
    Affected if Log entries show SQL injection payloads in PropertyID parameter values, indicating the vulnerability has been targeted.

You are affected if you are running ChurchCRM version 5.0.0 and the QueryView.php file with the PropertyID parameter is accessible without authentication and handles the parameter directly in 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries or prepared statements in QueryView.php to safely handle the PropertyID parameter, or update to a patched version if available. Input validation and proper escaping should also be applied as defense-in-depth.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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