Loading vulnerability…
ChurchCRM (open-source church management system) contains a SQL injection vulnerability in versions prior to 6.5.3 within a legacy, UI-removed but still web-reachable endpoint: /Reports/ConfirmReportEmail.php. The endpoint remains deployed and accessible directly by URL (dead but reachable code). Any authenticated user—including accounts with zero assigned permissions—can supply crafted input via the familyId parameter to trigger SQL injection, enabling unauthorized database query manipulation. The issue is fixed in ChurchCRM 6.5.3.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
familyId parameter, potentially resulting in unauthorized access to or modification of database contents (confidentiality/integrity compromise) and possibly broader application compromise depending on database permissions and reachable query primitives.If you can’t patch tonight, do this now.
/Reports/ConfirmReportEmail.php (e.g., delete the file from the web root, or block the path at the web server/WAF). Additionally, review and retire other legacy endpoints removed from the UI but still deployed, and audit for similar SQL injection patterns in legacy report/email confirmation code paths.Patch, then assume compromise.
/Reports/ConfirmReportEmail.php is removed or secured as part of the upgrade and verify no stale copies remain deployed.No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.