There is a SQL Injection vulnerability in ChurchCRM 4.4.5 via the 'PersonID' field in /churchcrm/WhyCameEditor.php.
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Link | Tags |
---|---|
https://github.com/ChurchCRM/CRM/issues/6005 | third party advisory issue tracking |
https://www.nu11secur1ty.com/2022/06/cve-2022-31325.htm | broken link |
https://github.com/nu11secur1ty/CVE-mitre/tree/main/2022/CVE-2022-31325 | third party advisory |
http://packetstormsecurity.com/files/167483/ChurchCRM-4.4.5-SQL-Injection.html | third party advisory vdb entry exploit |