CVE-2026-39329
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 · uneditedChurchCRM is an open-source church management system. Prior to 7.1.0, an SQL injection vulnerability was identified in /EventNames.php in ChurchCRM. Authenticated users with AddEvent privileges can inject SQL via the newEvtTypeCntLst parameter during event type creation. The vulnerable flow reaches an ON DUPLICATE KEY UPDATE clause where unescaped user input is interpolated directly. This vulnerability is fixed in 7.1.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 ChurchCRM's /EventNames.php allows authenticated users with AddEvent privileges to inject malicious SQL via the newEvtTypeCntLst parameter during event type creation. The unescaped user input is directly interpolated into an ON DUPLICATE KEY UPDATE clause, enabling attackers to manipulate database queries.
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< 7.1.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 ChurchCRM installation and versionLocate the ChurchCRM installation directory and check the version file (typically includes a version.php, composer.json, or package.json in the web root). Alternatively, check the database version table if accessible.Affected if The installed version is below 7.1.0 (e.g., 7.0.x, 2.x.x, etc.)
-
Verify EventNames.php existsCheck if the file /EventNames.php exists in the ChurchCRM web root directory.Affected if The file exists in the installation
-
Confirm vulnerable code pattern in EventNames.phpExamine EventNames.php source code and search for the newEvtTypeCntLst parameter usage. Look for direct interpolation of this parameter into an SQL ON DUPLICATE KEY UPDATE clause without escaping or prepared statements.Affected if The code directly uses $_POST['newEvtTypeCntLst'] or similar in an SQL query without escaping or parameterization
-
Check for AddEvent privilege configurationReview the user permission system in ChurchCRM. Check if any users or roles are assigned the AddEvent privilege. This can be done via the admin interface under User Management or by querying the user_privilege table in the database.Affected if Any user account has AddEvent privileges enabled, making that account capable of triggering the vulnerable code path
You are affected if you are running ChurchCRM version below 7.1.0, the EventNames.php file exists with the vulnerable parameter handling, and you have users with AddEvent privileges in your system.
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 · scoped7.1.0
Upgrade ChurchCRM to version 7.1.0 or later where the input is properly escaped/parameterized. If immediate upgrade is not feasible, implement strict input validation and use prepared statements for the affected code path.
7.1.0
- Backup your ChurchCRM database and application files before upgrading
- Download ChurchCRM version 7.1.0 from the official repository or release page
- Upload and extract the new version files to your web server, replacing the existing installation
- Run any database migration scripts included in the 7.1.0 release
- Verify the upgrade was successful by logging in and accessing the EventNames.php page
- Test that event type creation with the newEvtTypeCntLst parameter no longer exhibits SQL injection behavior
- Confirm existing functionality remains intact
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39329 — 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-39329 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