Skip to main content
VulnerabilityPublished Updated

CVE-2026-39344: ChurchCRM CRM · Basic XSS

Affects ChurchCRM CRMSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.1 High : upgrade to 7.1.0 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.0 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 7.1.0
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 30 Oct 2026.

What to do

Upgrade CRM and churchcrm/CRM to 7.1.0.

Affected software

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

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

AI-suggested

This vulnerability is fixed in ChurchCRM version 7.1.0. Users and administrators should upgrade to version 7.1.0 or later to remediate this issue. Since this is not a cloud service, patching the affected software is required. Patch status is confirmed by the vendor advisory stating the fix is included in version 7.1.0.

Description

A reflected Cross-Site Scripting (XSS) vulnerability exists in ChurchCRM versions prior to 7.1.0 on the login page. The vulnerability arises because the username parameter from the URL is not sanitized or encoded before being displayed in the login input field. This allows attackers to inject malicious JavaScript that executes in the victim's browser, potentially leading to theft of session cookies or manipulation of the login page display. The issue is fixed in version 7.1.0.

References

Community reviews

Loading reviews…