CVE-2026-35184
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 · uneditedEcclesiaCRM is CRM Software for church management. Prior to 8.0.0, there is a SQL injection vulnerability in v2/templates/query/queryview.php via the custom and value parameters. This vulnerability is fixed in 8.0.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 confidenceSQL injection vulnerability in EcclesiaCRM v2/templates/query/queryview.php via the 'custom' and 'value' parameters allows unauthenticated attackers to inject malicious SQL queries. This affects all versions prior to 8.0.0 of the church management software.
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< 8.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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed EcclesiaCRM versionLocate the EcclesiaCRM installation directory on the server. Check for version information in typical locations such as: composer.json file, includes/config.php (look for version constant), or a dedicated version.php file. Read the version number.Affected if The version is below 8.0.0 (any version prior to 8.0.0)
-
Verify the vulnerable file existsCheck if the file v2/templates/query/queryview.php exists within the web document root of the EcclesiaCRM installation.Affected if The file exists and the version is below 8.0.0
-
Inspect queryview.php for vulnerable parameter handlingOpen v2/templates/query/queryview.php in a text editor. Search for usage of the 'custom' and 'value' request parameters. Look for direct insertion of these parameters into SQL queries without prepared statements, parameter binding, or input sanitization.Affected if The code shows unsanitized use of 'custom' or 'value' parameters in SQL query construction
-
Review web access logs for exploitation indicatorsExamine web server access logs (Apache access.log, Nginx access.log) for requests to queryview.php. Search for unusual characters in 'custom' or 'value' parameters such as quotes, UNION statements, or SQL keywords that may indicate injection attempts.Affected if Suspicious SQL injection patterns are present in recent access logs targeting this endpoint
The environment is affected if EcclesiaCRM version is below 8.0.0 and the queryview.php file with vulnerable parameter handling is present and accessible.
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.
dbcve · scoped8.0.0
Upgrade to EcclesiaCRM version 8.0.0 or later. If immediate upgrade is not feasible, implement input validation and parameterized queries for the affected parameters.
8.0.0
- Upgrade EcclesiaCRM to version 8.0.0 or later to resolve the SQL injection vulnerability in v2/templates/query/queryview.php via the custom and value parameters
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-35184 — 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-2026-35184 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