CVE-2025-7929

7.3 HIGH

📋 TL;DR

A critical SQL injection vulnerability exists in Church Donation System 1.0 where the fname parameter in /members/edit_Members.php is not properly sanitized. This allows remote attackers to execute arbitrary SQL commands on the database. All users running Church Donation System 1.0 are affected.

💻 Affected Systems

Products:
  • Church Donation System
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability affects the default installation. Other parameters beyond fname may also be vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, data manipulation, and potential remote code execution via database functions.

🟠

Likely Case

Unauthorized access to sensitive donor information, financial data manipulation, and potential privilege escalation.

🟢

If Mitigated

Limited data exposure if proper input validation and database permissions are in place.

🌐 Internet-Facing: HIGH - The vulnerability is remotely exploitable and affects web-facing systems.
🏢 Internal Only: MEDIUM - Internal systems are still vulnerable but attack surface is reduced.

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploit details are publicly available on GitHub. The vulnerability requires no authentication and has simple exploitation vectors.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://code-projects.org/

Restart Required: No

Instructions:

No official patch available. Consider migrating to alternative software or implementing workarounds.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Implement proper input validation and parameterized queries for all user inputs in edit_Members.php

Manual code modification required - no automated commands

Web Application Firewall (WAF)

all

Deploy a WAF with SQL injection protection rules to block malicious requests

Depends on WAF solution - configure SQL injection protection rules

🧯 If You Can't Patch

  • Disable or restrict access to /members/edit_Members.php via web server configuration
  • Implement network segmentation and restrict database access to only necessary systems

🔍 How to Verify

Check if Vulnerable:

Test the fname parameter in /members/edit_Members.php with SQL injection payloads like ' OR '1'='1

Check Version:

Check software version in admin panel or configuration files

Verify Fix Applied:

Verify that SQL injection payloads no longer execute and return proper error handling

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL syntax in HTTP request logs
  • Multiple failed login attempts from edit_Members.php
  • Database error messages in application logs

Network Indicators:

  • SQL keywords in HTTP POST requests to edit_Members.php
  • Unusual database connection patterns

SIEM Query:

source="web_logs" AND uri="/members/edit_Members.php" AND (request CONTAINS "UNION" OR request CONTAINS "SELECT" OR request CONTAINS "OR '1'='1'")

🔗 References

📤 Share & Export