Skip to main content
VulnerabilityPublished

CVE-2025-68401: ChurchCRM CRM · Cross-site Scripting

Affects ChurchCRM CRMSource CVE Database V5

0

Not known to be exploited · CVSS 6.2 Medium : upgrade to 6.0.0 when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score
6.2Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.0.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade churchcrm/CRM to 6.0.0.

Affected software

ProductAffectedFixed in
GitHubchurchcrm/CRMpkg:github/churchcrm/CRMOther threatsAffected
  • <6.0.0
Fixed in
  • 6.0.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately upgrade ChurchCRM installations to version 6.0.0 or later, which contains the necessary patches to sanitize and encode user input properly. Additionally, administrators should enforce secure cookie attributes, including HttpOnly and Secure flags, to prevent client-side script access to session cookies. Implement Content Security Policy (CSP) headers to restrict execution of unauthorized scripts and reduce XSS impact. Conduct regular security audits and input validation reviews on all user-generated content fields. Educate users to recognize suspicious content and avoid interacting with untrusted inputs. Where possible, isolate ChurchCRM instances behind web application firewalls (WAFs) configured to detect and block XSS payloads. Finally, monitor logs for unusual activity indicative of exploitation attempts.

Description

ChurchCRM is an open-source church management system. Prior to version 6.0.0, the application stores user-supplied HTML/JS without sufficient sanitization/encoding. When other users later view this content, attacker-controlled JavaScript executes in their browser (stored XSS). In affected contexts the script can access web origin data and perform privileged actions as the victim. Where session cookies are not marked HttpOnly, the script can read document.cookie, enabling session theft and account takeover. Version 6.0.0 patches the issue.

References

Community reviews

Loading reviews…