CVE-2005-2473

Description

Multiple SQL injection vulnerabilities in ChurchInfo allow remote attackers to execute arbitrary SQL commands via the PersonID parameter to (1) PersonView.php, (2) MemberRoleChange.php, (3) PropertyAssign.php, (4) WhyCameEditor.php, (5) GroupPropsEditor.php, (6) Reports/PDFLabel.php, or (7) UserDelete.php, (8) DepositSlipID parameter to DepositSlipEditor.php, (9) QueryID parameter to QueryView.php, GroupID parameter to (10) GroupView.php, (11) GroupMemberList.php, (12) MemberRoleChange.php, (13) GroupDelete.php, (14) /Reports/ClassAttendance.php, or (15) /Reports/GroupReport.php, (16) PropertyID parameter to PropertyEditor.php, FamilyID parameter to (17) Canvas05Editor.php, (18) CanvasEditor.php, or (19) FamilyView.php, or (20) PledgeID parameter to PledgeDetails.php.

7.5

CVSS

Severity: High

CVSS 2.0 •

EPSS 2.12% Top 20%

Third-Party Advisory secunia.com

Affected: n/a n/a

References

Link	Tags
http://www.osvdb.org/18416	vdb entry
http://www.osvdb.org/18411	vdb entry
http://www.osvdb.org/18423	vdb entry
http://marc.info/?l=bugtraq&m=112291550713546&w=2	mailing list
http://www.osvdb.org/18421	vdb entry
http://www.osvdb.org/18418	vdb entry
http://www.osvdb.org/18413	vdb entry
http://www.securityfocus.com/bid/14438	vdb entry
http://www.osvdb.org/18417	vdb entry
http://securitytracker.com/id?1014617	vdb entry
http://www.osvdb.org/18420	vdb entry
http://www.osvdb.org/18415	vdb entry
http://www.osvdb.org/18428	vdb entry
http://www.osvdb.org/18414	vdb entry
http://www.osvdb.org/18427	vdb entry
http://www.osvdb.org/18422	vdb entry
http://www.osvdb.org/18410	vdb entry
http://www.osvdb.org/18412	vdb entry
http://www.osvdb.org/18408	vdb entry
http://www.osvdb.org/18424	vdb entry
http://www.osvdb.org/18409	vdb entry
https://exchange.xforce.ibmcloud.com/vulnerabilities/21647	vdb entry
http://www.osvdb.org/18419	vdb entry
http://secunia.com/advisories/16292	third party advisory

Frequently Asked Questions

What is the severity of CVE-2005-2473?: CVE-2005-2473 has been scored as a high severity vulnerability.
How to fix CVE-2005-2473?: To fix CVE-2005-2473, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2005-2473 being actively exploited in the wild?: It is possible that CVE-2005-2473 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~2% probability that this vulnerability will be exploited by malicious actors in the next 30 days.