CVE-2025-7859
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-7859 is a critical SQL injection vulnerability in the Church Donation System version 1.0, specifically in the /members/update_password_admin.php file. It occurs because the 'new_password' parameter is not properly sanitized or validated before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely without authentication, potentially gaining unauthorized access to the database, modifying or deleting data, and compromising system integrity. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data tampering, and full system control by attackers. It can also cause service disruption. Since exploitation requires no authentication and can be performed remotely, it poses a significant risk to confidentiality, integrity, and availability of the affected system's data and services. [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 the endpoint /members/update_password_admin.php is accessible and vulnerable to SQL injection via the 'new_password' parameter. One method is to perform targeted testing using SQL injection payloads in POST requests to this endpoint. Additionally, Google dorking can be used to find vulnerable targets by searching for "inurl:members/update_password_admin.php". Specific commands to test might include curl commands sending crafted POST requests with SQL injection payloads in the 'new_password' parameter, such as boolean-based, error-based, or time-based blind injection payloads. For example, using curl to send a POST request with a payload that triggers a time delay (e.g., SLEEP()) can help confirm vulnerability. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing the affected component with an alternative product if possible, as no known mitigations are documented; 2) Implementing prepared statements with parameter binding to separate SQL code from user input; 3) Applying strict input validation and filtering on the 'new_password' parameter to ensure it conforms to expected formats; 4) Limiting database user permissions to the minimum necessary, avoiding use of high-privilege accounts such as 'root' or 'admin' for routine operations. These steps help prevent SQL injection exploitation and protect system security and data integrity. [2, 3, 1]