Skip to content
Sign in
CVE-2026-445479.6CriticalCWE-304

CVE-2026-44547: ChurchCRM: Incomplete fix for CVE-2026-40582: public API login still bypasses 2FA and account lockout in ChurchCRM 7.2.2

ChurchCRM · CRM

Affected: ChurchCRM CRM · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.3%probability of exploitation in the next 30 days
18th percentile
050100

Higher than 18% of scored CVEs

9.6CriticalCVSS 3.1
LowCrit.

DescriptionCVE.org

ChurchCRM is an open-source church management system. From 7.2.0 to 7.2.2, The fix for CVE-2026-4058 is incomplete. The hardening commit was merged and then silently stripped from src/api/routes/public/public-user.php by an unrelated PR before any 7.2.x tag was cut. Every shipped 7.2.x release therefore remains exploitable by the PoC published with the original advisory. This vulnerability is fixed in 7.3.1.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • ChurchCRM · CRM>= 7.2.0, < 7.3.1

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Vendor
ChurchCRM
Published
May 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-44547 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

Updated AboutDevelopersSign in