CVE-2025-7833

7.3 HIGH

📋 TL;DR

This critical SQL injection vulnerability in Church Donation System 1.0 allows attackers to manipulate database queries through the Amount parameter in /members/giving.php. Remote attackers can potentially read, modify, or delete sensitive donation data and user information. All installations of Church Donation System 1.0 with the vulnerable file accessible are affected.

💻 Affected Systems

Products:
  • Church Donation System
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Any installation with /members/giving.php accessible is vulnerable. The system appears to be a PHP-based web application.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including exfiltration of all donation records, user credentials, and financial data, followed by database destruction or ransomware deployment.

🟠

Likely Case

Unauthorized access to donation records and user information, potential data theft, and manipulation of financial records.

🟢

If Mitigated

Limited impact with proper input validation and database permissions, potentially only error messages or limited data exposure.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploit details are publicly available on GitHub. SQL injection vulnerabilities are commonly weaponized with automated tools.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

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

Restart Required: No

Instructions:

No official patch available. Check vendor website for updates. Consider implementing parameterized queries and input validation in /members/giving.php.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Add server-side validation to ensure Amount parameter contains only numeric values

Edit /members/giving.php to add: if(!is_numeric($_POST['Amount'])) { die('Invalid input'); }

Web Application Firewall (WAF)

all

Deploy WAF rules to block SQL injection patterns

Add WAF rule: Detect and block SQL injection patterns in POST parameters

🧯 If You Can't Patch

  • Restrict access to /members/giving.php using IP whitelisting or authentication
  • Implement database user with minimal permissions (read-only if possible)

🔍 How to Verify

Check if Vulnerable:

Test /members/giving.php with SQL injection payloads like: Amount=1' OR '1'='1

Check Version:

Check application files or documentation for version information

Verify Fix Applied:

Test with same payloads after implementing fixes - should return error or sanitized response

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL errors in application logs
  • Multiple failed login attempts following SQL injection patterns
  • Unexpected database queries from web server

Network Indicators:

  • HTTP POST requests to /members/giving.php with SQL keywords in parameters
  • Unusual database traffic patterns from web server

SIEM Query:

source="web_logs" AND uri="/members/giving.php" AND (payload="' OR" OR payload="UNION" OR payload="SELECT" OR payload="--")

🔗 References

📤 Share & Export