Skip to main content
VulnerabilityPublished

CVE-2026-24854: ChurchCRM CRM · SQL Injection

Affects ChurchCRM CRMSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High : upgrade to 6.7.2 soon.

Data as of 26 Oct 2026, 14:05 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jan 2026

  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 CRM and churchcrm/CRM to 6.7.2.

Affected software

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

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 to version 6.7.2 or later, which contains the official patch for this vulnerability. Until the upgrade is applied, organizations should restrict access to the /PaddleNumEditor.php endpoint to trusted users only and implement strict authentication and monitoring controls to detect anomalous database queries. Employing Web Application Firewalls (WAFs) with SQL Injection detection rules can help mitigate exploitation attempts. Regularly audit user permissions to ensure no unnecessary accounts have authentication access, and enforce strong password policies to reduce the risk of account compromise. Additionally, database activity monitoring should be enabled to detect suspicious SQL commands. Organizations should also review logs for any signs of attempted exploitation and prepare incident response plans specific to SQL Injection attacks.

Description

ChurchCRM is an open-source church management system. A SQL Injection vulnerability exists in endpoint `/PaddleNumEditor.php` in ChurchCRM prior to version 6.7.2. Any authenticated user, including one with zero assigned permissions, can exploit SQL injection through the `PerID` parameter. Version 6.7.2 contains a patch for the issue.

References

Community reviews

Loading reviews…