CVE-2025-7929
BaseFortify
Publication date: 2025-07-21
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| carmelo | church_donation_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-7929 is a critical SQL injection vulnerability in version 1.0 of the Church Donation System, specifically in the /members/edit_Members.php file. The vulnerability occurs because the 'fname' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This can lead to unauthorized access to the database, enabling attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can result in unauthorized database access, data leakage, data manipulation, and potentially full system compromise or service disruption. It compromises the confidentiality, integrity, and availability of the system's data, putting sensitive information at risk and potentially disrupting normal operations. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by identifying if your system is running version 1.0 of the Church Donation System with the vulnerable file /members/edit_Members.php. You can use Google dorking to find potentially vulnerable targets by searching for "inurl:members/edit_Members.php". On your system, you can check for the presence of this file and version. Additionally, to detect SQL injection attempts, you can monitor web server logs for suspicious input in the 'fname' parameter that includes SQL syntax. For example, using grep on access logs: grep 'fname=' /var/log/apache2/access.log. You can also use tools like sqlmap to test the vulnerability by targeting the URL with the vulnerable parameter. Example command: sqlmap -u "http://target/members/edit_Members.php?fname=test" --batch --risk=3 --level=5 [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements (parameterized queries) to handle the 'fname' parameter safely, ensuring that user inputs are treated strictly as data and not executable code. Additionally, apply rigorous input validation and filtering to ensure inputs conform to expected formats. Restrict database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. If possible, update or patch the system to a fixed version once available. Until then, consider disabling or restricting access to the vulnerable functionality to prevent exploitation. [2]