High 7.2Published Jan 30, 2026

CVE-2026-24855ChurchCRM has Stored Cross-Site Scripting (XSS) in Create Events in Church Calendar, Leading to Account Takeover

Updated under an hour ago (Oct 27, 2026, 12:10 AM ET)

Does this affect you?

It affects ChurchCRM CRM and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for ChurchCRM CRM

Exploited in the last 30 days

ChurchCRM is an open-source church management system. Versions prior to 6.7.2 have a Stored Cross-Site Scripting (XSS) vulnerability occurs in Create Events in Church Calendar. Users with low privileges can create XSS payloads in the Description field. This payload is stored in the database, and when other users view that event (including the admin), the payload is triggered, leading to account takeover. Version 6.7.2 fixes the vulnerability.

CVSS: 7.2 HIGH (v4.0, CNA)CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:H/VA:N/SC:H/SI:H/SA:H/E:P
Weakness (CWE): CWE-79
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: GitHub_M
NVD analysis: Analyzed
Record last updated: Jan 30, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

ChurchCRM CRM churchcrm:crm (from the name)	before 6.7.2	CNA record
churchcrm churchcrm churchcrm:churchcrm	before 6.7.2	NVD

References

References

https://github.com/ChurchCRM/CRM/security/advisories/GHSA-49qp-cfqx-c767	x-refsource-confirm, exploit, vendor-advisory
https://github.com/ChurchCRM/CRM/commit/0cd0d211459b8c19509d36b3c1dfcd7f8c10d914	x-refsource-misc, patch
https://github.com/ChurchCRM/CRM/commit/ec4b16e9a3ca09c8a01a712bcb90579c42f2ba28	x-refsource-misc, patch

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.