CVE-2024-25895: CRM · n/a
Affects CRMSource CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Feb 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubchurchcrm/CRMpkg:github/churchcrm/CRMOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until an official patch is released, organizations should implement several specific mitigations: 1) Employ web application firewalls (WAFs) with rules to detect and block reflected XSS payloads targeting the 'type' parameter in /EventAttendance.php. 2) Educate users and administrators about the risks of clicking untrusted links, especially those purporting to come from ChurchCRM. 3) Implement Content Security Policy (CSP) headers to restrict the execution of inline scripts and reduce the impact of XSS attacks. 4) Review and sanitize all user inputs on the server side, particularly the 'type' parameter, if custom modifications or temporary fixes are possible. 5) Monitor web server logs for suspicious requests containing script tags or unusual parameters targeting /EventAttendance.php. 6) Isolate ChurchCRM instances from critical internal networks to limit lateral movement if exploitation occurs. 7) Plan for rapid deployment of official patches once available and test updates in a staging environment before production rollout.
Description
A reflected cross-site scripting (XSS) vulnerability in ChurchCRM 5.5.0 allows remote attackers to inject arbitrary web script or HTML via the type parameter of /EventAttendance.php