CVE-2025-7861
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-7861 is a critical SQL injection vulnerability in version 1.0 of the Church Donation System, specifically in the /members/search.php file. The vulnerability occurs because the 'username' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, potentially leading to data retrieval, modification, or deletion. The attack can be launched remotely without authentication, making it easy for attackers to exploit. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to sensitive data, data leakage, data tampering, and potential full system control. It can also cause service disruption and compromise the confidentiality, integrity, and availability of the system. Since no authentication is required to exploit it, attackers can remotely launch attacks easily, putting the system and its data at significant risk. [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/search.php endpoint for SQL injection on the 'username' parameter. A known payload for detection is a boolean-based blind SQL injection such as: username=123' OR NOT 2163=2163 # sent via a POST request. Tools like sqlmap can be used to automate detection and database enumeration. Additionally, vulnerable targets can be identified using Google dorking with the query: inurl:members/search.php. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Implement strict input validation and filtering to ensure inputs conform to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. If possible, replace the affected software with an alternative product as no known countermeasures have been reported. [2, 3]