CVE-2025-7860
BaseFortify
Publication date: 2025-07-20
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-7860 is a critical SQL injection vulnerability in version 1.0 of the Church Donation System, specifically in the /members/login_admin.php file. It occurs because the 'username' parameter in the login form is not properly sanitized or validated, allowing attackers to inject malicious SQL code. This flaw enables unauthorized access to the database by manipulating SQL queries, potentially leading to data leakage, modification, or deletion. The vulnerability can be exploited remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to sensitive data, data tampering, deletion, and full system compromise. Attackers can remotely execute malicious SQL queries without authentication, potentially disrupting services and exposing confidential information stored in the database. This poses a severe security risk to the affected system's confidentiality, integrity, and availability. [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 testing the /members/login_admin.php endpoint for SQL injection on the 'username' parameter. You can use tools like sqlmap to automate detection. For example, a command using sqlmap would be: sqlmap -u "http://target/members/login_admin.php" --data="username=1&password=any" -p username --batch. Additionally, manual testing with payloads such as 'username=1' AND 5447=5447 AND 'efLX'='efLX' or time-based payloads like 'username=1' AND (SELECT SLEEP(5)) AND 'YqXT'='YqXT' in a POST request can help confirm the vulnerability. Google dorking with queries like inurl:members/login_admin.php can help identify potentially vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Applying strict input validation and filtering on the 'username' parameter to ensure it conforms to expected formats. 3) Limiting database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. 4) If possible, replacing the affected component with an alternative product. These measures help protect system security and maintain data integrity. [1, 2, 3]