dbcve.org
ChurchinfoApplication

CVE-2005-2473

HIGH · 7.5 CVSS v2.0 Published 2005-08-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

ChurchInfo contains multiple SQL injection vulnerabilities in 20 different PHP files (PersonView.php, MemberRoleChange.php, GroupView.php, etc.). Remote attackers can execute arbitrary SQL commands by injecting malicious input through parameters like PersonID, GroupID, FamilyID, and PledgeID without proper input sanitization or parameterized queries.

MitigationReplace all string concatenation in SQL queries with parameterized queries/prepared statements, and implement strict input validation on all user-supplied parameters across the affected PHP files.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChurchinfoApplication
Affected:= 1.1.1= 1.1.2= 1.1.3= 1.1.4= 1.1.5= 1.1.6= 1.2.0= 1.2.1= 1.2.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify ChurchInfo installation and version
    Locate the ChurchInfo application directory and check for a version file or header (commonly in setup, include files, or the main index page). Look for version strings like '1.1.1', '1.1.2', '1.1.3', '1.1.4', '1.1.5', '1.1.6', '1.2.0', '1.2.1', or '1.2.2 in source files or configuration.
    Affected if The installed version matches any of: 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.2.0, 1.2.1, or 1.2.2
  2. Locate vulnerable PHP files
    Search the ChurchInfo web directory for these PHP files mentioned in the advisory: PersonView.php, MemberRoleChange.php, GroupView.php, and similar files that handle PersonID, GroupID, FamilyID, or PledgeID parameters.
    Affected if Any of these PHP files exist in the web-accessible directory
  3. Inspect SQL query handling in vulnerable files
    Open each identified vulnerable PHP file and examine how SQL queries are constructed. Search for query patterns that concatenate user-supplied parameters directly into SQL strings (e.g., 'SELECT * FROM table WHERE id=' . $_GET['PersonID']).
    Affected if SQL queries concatenate request parameters (PersonID, GroupID, FamilyID, PledgeID) without using prepared statements or escaping functions
  4. Verify parameter input is accessible
    Confirm the affected parameters (PersonID, GroupID, FamilyID, PledgeID) are received from GET or POST requests and used in SQL queries without sanitization. Check if these parameters are passed through $_GET, $_POST, or $_REQUEST.
    Affected if User-supplied input for these parameters flows directly into SQL queries without validation or parameterization

The environment is affected if ChurchInfo versions 1.1.1 through 1.2.2 are installed and the vulnerable PHP files handle SQL queries by concatenating PersonID, GroupID, FamilyID, or PledgeID parameters without prepared statements.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace all string concatenation in SQL queries with parameterized queries/prepared statements, and implement strict input validation on all user-supplied parameters across the affected PHP files.

Fix this in Churchinfo Scoped from the published advisory
  • Consultation6.0 h
  • Implementation32.0 h
  • Testing12.0 h
  • Review / QA6.0 h
56.0 hours of engineering $9,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2005-2473 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2005-2473 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data