CVE-2025-7928
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-7928 is a critical SQL injection vulnerability in version 1.0 of the Church Donation System, specifically in the /members/edit_user.php file. It occurs because the "firstname" parameter is not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, potentially manipulating the database by accessing, modifying, or deleting data. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, data leakage, data tampering, deletion of data, full system control, and potential service disruption. Attackers can remotely execute arbitrary SQL commands without needing to authenticate, compromising the confidentiality, integrity, and availability of the system. [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 'firstname' parameter in POST requests to the /members/edit_user.php file for SQL injection. A proof-of-concept payload uses a boolean-based blind SQL injection with MySQL's RLIKE operator, for example: firstname=1' RLIKE (SELECT (CASE WHEN (6327=6327) THEN 1 ELSE 0x28 END)) AND 'eZZR'='eZZR. Tools like sqlmap can be used to automate detection and enumerate the database structure. Additionally, vulnerable targets can be identified using Google dorking with queries such as "inurl:members/edit_user.php" to find exposed instances. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Applying strict input validation and filtering on the 'firstname' parameter and other inputs to ensure they conform to expected formats. 3) Limiting database user permissions to the minimum necessary, avoiding use of high-privilege accounts like 'root' or 'admin' for routine operations. If possible, replace the affected component with an alternative product. These steps help protect system security and maintain data integrity. [2, 3, 1]