Skip to content
Fencer Intel
high 7.2

CVE-2022-31325 json

There is a SQL Injection vulnerability in ChurchCRM 4.4.5 via the 'PersonID' field in /churchcrm/WhyCameEditor.php.

published 4y ago modified 4mo ago also EUVD-2022-52867

cvss
7.2
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
5.2%
EPSS 5.2% chance of exploitation in 30 days, percentile 92%
public exploits
1
Exploit-DB

Summary

There is a SQL Injection vulnerability in ChurchCRM 4.4.5 via the 'PersonID' field in /churchcrm/WhyCameEditor.php.

Is CVE-2022-31325 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. Published
  2. First public exploit (EDB-50965)

Exploit prediction

5.22% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-50965 ChurchCRM 4.4.5 - SQLi webapps, 2022-06-14
  • packetstormsecurity.com http://packetstormsecurity.com/files/167483/ChurchCRM-4.4.5-SQL-Injection.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P

Classification

Weakness
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.