CVE-2026-39331: ChurchCRM is an open-source church management system

Q: How do I fix CVE-2026-39331?

churchcrm: upgrade to 7.1.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-39331 being exploited?

CVE-2026-39331 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-39331 affect?

CVE-2026-39331 affects churchcrm. Severity is high (CVSS 8.1). ChurchCRM is an open-source church management system. Prior to 7.1.0, an authenticated API user can modify any family record's state without proper authorization by simply changing the {familyId} parameter in requests, regardless of whether

Routine

HIGH 8.1UPGRADE

CVE-2026-39331 is a high-severity flaw (CVSS 8.1) affecting churchcrm. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

ChurchCRM is an open-source church management system. Prior to 7.1.0, an authenticated API user can modify any family record's state without proper authorization by simply changing the {familyId} parameter in requests, regardless of whether they possess the required EditRecords privilege. /family/{familyId}/verify, /family/{familyId}/verify/url, /family/{familyId}/verify/now, /family/{familyId}/activate/{status}, and /family/{familyId}/geocode la

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.2% (top 88%)
CISA exploited list	No
Weakness	CWE-639, CWE-863
Published	2026-04-07
Last modified	2026-10-26

Publisher (CNA): GitHub, Inc. · Vendor: churchcrm

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-04-07 18:16 UTCPublished CVE record published
2026-10-26 21:10 UTCUpdated Record last modified

churchcrm churchcrm UPGRADE

Affected: < 7.1.0

Fixed in: 7.1.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy churchcrm || rpm -q churchcrm || churchcrm --version

2. UPGRADE to 7.1.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade churchcrm

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade churchcrm

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-39331?

churchcrm: upgrade to 7.1.0. Exact commands for each OS are on this page.

Is CVE-2026-39331 being exploited?

CVE-2026-39331 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-39331 affect?

CVE-2026-39331 affects churchcrm. Severity is high (CVSS 8.1). ChurchCRM is an open-source church management system. Prior to 7.1.0, an authenticated API user can modify any family record's state without proper authorization by simply changing the {familyId} parameter in requests, regardless of whether

How urgent is CVE-2026-39331?

Priority 31/100. High severity

Related CVEs

CVE-2026-35573 CRITICAL 9.1 UPGRADE ChurchCRM is an open-source church management system
CVE-2026-39318 HIGH 8.8 UPGRADE ChurchCRM is an open-source church management system
CVE-2026-35574 HIGH 7.3 UPGRADE ChurchCRM is an open-source church management system
CVE-2026-39328 HIGH 8.9 UPGRADE ChurchCRM is an open-source church management system
CVE-2026-39333 HIGH 8.7 UPGRADE ChurchCRM is an open-source church management system

References

← Back to latest CVEs