CVE-2023-38770
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 · uneditedSQL injection vulnerability in ChurchCRM v.5.0.0 allows a remote attacker to obtain sensitive information via the group 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 confidenceSQL injection vulnerability in ChurchCRM v5.0.0 in the group parameter of /QueryView.php allows remote attackers to inject malicious SQL queries, potentially exposing sensitive database contents including user data, financial records, or configuration information.
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= 5.0.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm ChurchCRM versionCheck the installed ChurchCRM version by examining the version file, composer.json, or the system information page in the admin dashboard. Common locations include /composer.json or the 'About' page in the web interface.Affected if The installed version is exactly 5.0.0 (the only affected version per the provided advisory)
-
Locate QueryView.phpVerify the existence of QueryView.php in the web root or src directory of the ChurchCRM installation. Check paths such as /QueryView.php or /src/QueryView.php depending on the installation structure.Affected if QueryView.php exists and is accessible via the web server
-
Test for SQL injection vulnerabilityIf QueryView.php is accessible, inspect the source code for the 'group' parameter handling. Look for database queries that incorporate the 'group' parameter without using prepared statements or parameterized queries. Search for patterns like '$_GET['group']' or 'Request::get' concatenated directly into SQL strings.Affected if The 'group' parameter is used in SQL queries without parameterized binding or input sanitization
-
Check database user privilegesReview the database configuration file (often config.php or similar) to determine what database user privileges the application uses. Assess whether the database user has permissions that could allow data exfiltration if SQL injection succeeds.Affected if The application database user has broad permissions (such as SELECT on sensitive tables)
-
Review web server access logsExamine web server access logs for suspicious requests to QueryView.php with unusual characters in the 'group' parameter, such as quotes, UNION statements, or boolean-based injection patterns.Affected if Malicious SQL injection payloads appear in access logs for QueryView.php
The environment is affected if ChurchCRM version 5.0.0 is running and the QueryView.php file handles the 'group' parameter without parameterized queries.
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.
From vendor dataImplement prepared statements/parameterized queries for all database operations involving the group parameter, apply input validation and sanitization, and consider updating to a patched version if available.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-38770 — 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-2023-38770 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