dbcve.org
ChurchinfoApplication

CVE-2005-2474

MEDIUM · 5.0 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 →
59/100
Remediation priority · Elevated
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
ChurchInfo allows remote attackers to execute obtain sensitive information 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, an invalid Number parameter to (8) SelectList.php or (9) SelectDelete.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, which reveal the path in an error message.

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 versions prior to undisclosed patches contain multiple path disclosure vulnerabilities in at least 20 PHP files (PersonView.php, MemberRoleChange.php, PropertyAssign.php, SelectList.php, GroupView.php, PropertyEditor.php, Canvas05Editor.php, PledgeDetails.php, etc.). Attackers can obtain sensitive path information by supplying invalid values to parameters including PersonID, Number, GroupID, PropertyID, FamilyID, and PledgeID, which cause the application to reveal full server paths in error messages.

MitigationImplement proper input validation and error handling across all affected PHP files to prevent path disclosure. Configure the web server and PHP to display generic error messages rather than detailed stack traces, and validate all user-supplied parameters before processing.

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
None
Availability
None

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

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 version
    Check the version file, release notes, or the application admin interface for the installed ChurchInfo version number
    Affected if The installed version is 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. Test PersonView.php for path disclosure
    Access PersonView.php with an invalid PersonID parameter value (such as a non-existent ID or special characters) and observe the error output
    Affected if The error message displays the full server file system path (e.g., /var/www/html/churchinfo/...)
  3. Test MemberRoleChange.php for path disclosure
    Access MemberRoleChange.php with an invalid Number parameter value and check the error response
    Affected if The error message reveals the complete server path
  4. Test PropertyAssign.php and PropertyEditor.php
    Access these files with invalid PropertyID parameters and examine any error messages
    Affected if Full server paths appear in the error output
  5. Test GroupView.php and SelectList.php
    Submit invalid GroupID values to GroupView.php and SelectList.php, then inspect error messages for path disclosure
    Affected if The application returns full system paths in error messages

If the installed version matches 1.1.1 through 1.2.2 and supplying invalid values to parameters like PersonID, Number, GroupID, or PropertyID reveals full server file paths in error messages, the environment is affected by this path disclosure vulnerability.

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

Implement proper input validation and error handling across all affected PHP files to prevent path disclosure. Configure the web server and PHP to display generic error messages rather than detailed stack traces, and validate all user-supplied parameters before processing.

Fix this in Churchinfo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,650
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2005-2474 — 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-2474 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