CVE-2025-7832
BaseFortify
Publication date: 2025-07-19
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-7832 is a critical SQL injection vulnerability in the Church Donation System version 1.0, specifically in the /members/offering.php file. It occurs because the 'trcode' 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 leakage, modification, deletion, and full system compromise. The attack can be performed remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access to sensitive data, data manipulation, deletion, and exposure of confidential information. It can also result in full system compromise and service disruption. Since the exploit requires no authentication and can be initiated remotely, it poses a high risk to affected systems, potentially impacting confidentiality, integrity, and availability of 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 testing the "trcode" parameter in the /members/offering.php file for SQL injection flaws. Tools like sqlmap can be used to automate detection and exploitation attempts. Example commands include using sqlmap with a POST request targeting the vulnerable parameter. Additionally, manual testing with SQL injection payloads such as boolean-based blind, error-based, and time-based blind techniques can be performed. For instance, sending crafted POST requests with payloads that include SQL functions like SLEEP or RLIKE to observe abnormal behavior or delays can help identify the vulnerability. Attackers may also use Google dorking with queries like "inurl:members/offering.php" to find vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to ensure user input is properly separated from SQL code, thereby preventing injection. Rigorous input validation and filtering should be applied to the "trcode" parameter to ensure it conforms to expected formats. Minimizing database user permissions by avoiding the use of high-privilege accounts for routine operations is also recommended. If possible, replacing the affected software with an alternative product is advised, as no known countermeasures or patches are documented. These measures help protect system security and maintain data integrity. [2, 3]