CVE-2025-7928

7.3 HIGH

📋 TL;DR

This critical SQL injection vulnerability in Church Donation System 1.0 allows remote attackers to execute arbitrary SQL commands via the 'firstname' parameter in the /members/edit_user.php file. Attackers can potentially access, modify, or delete database content. All users running Church Donation System 1.0 are affected.

💻 Affected Systems

Products:
  • Church Donation System
Versions: 1.0
Operating Systems: All platforms running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: Affects the specific file /members/edit_user.php, but other parameters may also be vulnerable as noted in the description.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, data destruction, authentication bypass, and potential remote code execution if database permissions allow.

🟠

Likely Case

Unauthorized access to sensitive donor information, financial data, and user credentials stored in the database.

🟢

If Mitigated

Limited impact with proper input validation and database permission restrictions, though SQL injection attempts would still be logged.

🌐 Internet-Facing: HIGH - The vulnerability is remotely exploitable and affects a web application component.
🏢 Internal Only: MEDIUM - Internal systems could still be targeted via phishing or compromised internal accounts.

🎯 Exploit Status

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

Exploit details are publicly available on GitHub, making this easily exploitable by attackers with basic SQL injection knowledge.

🛠️ 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 Filter

all

Add server-side input validation to sanitize the 'firstname' parameter and other user inputs

Edit /members/edit_user.php to add parameterized queries or input sanitization

Web Application Firewall

all

Deploy WAF rules to block SQL injection patterns

Configure WAF to detect and block SQL injection attempts on /members/edit_user.php

🧯 If You Can't Patch

  • Restrict access to /members/edit_user.php using IP whitelisting or authentication requirements
  • Implement database-level controls: use least privilege accounts, enable audit logging, and regular backups

🔍 How to Verify

Check if Vulnerable:

Test the /members/edit_user.php endpoint with SQL injection payloads in the 'firstname' parameter

Check Version:

Check the software version in the application interface or configuration files

Verify Fix Applied:

Verify that SQL injection attempts no longer succeed and that input validation is properly implemented

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL error messages in application logs
  • Multiple failed login attempts or parameter manipulation

Network Indicators:

  • HTTP requests to /members/edit_user.php with SQL keywords in parameters
  • Unusual database query patterns

SIEM Query:

source="web_logs" AND uri="/members/edit_user.php" AND (param="firstname" AND value CONTAINS "' OR '1'='1" OR value CONTAINS "UNION SELECT" OR value CONTAINS "--")

🔗 References

📤 Share & Export