CVE-2025-7831
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-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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-7831 is a critical SQL injection vulnerability in the Church Donation System version 1.0, specifically in the /members/Tithes.php file. It occurs because the 'trcode' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This flaw enables unauthorized execution of SQL commands on the database, potentially leading to unauthorized data access, 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 leakage, data tampering, and potential full system compromise. Attackers can retrieve, modify, or delete data in the database, compromising confidentiality, integrity, and availability of the system. Since no authentication is required, the risk is higher, and the attack can be initiated remotely. This poses a severe threat to system security and business continuity. [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/Tithes.php file for SQL injection. Tools like sqlmap can be used to confirm the vulnerability and enumerate the database. Example payloads for manual testing include boolean-based blind injection, error-based injection, and time-based blind injection techniques. For instance, using curl or a similar tool, you can send POST requests with payloads such as: curl -X POST -d "amount=2&trcode=2' AND (SELECT 6597 FROM (SELECT(SLEEP(5)))nfRZ) AND 'hnvD'='hnvD&save=" http://target/members/Tithes.php This will help detect time-based blind SQL injection. Additionally, Google dorking with the query inurl:members/Tithes.php can help locate vulnerable instances on the internet. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL code from user input, enforcing strict input validation and filtering on the 'trcode' parameter to ensure it conforms to expected formats, and restricting database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. Since no official vendor patch or mitigation is available, replacing the affected component with an alternative product is also suggested. [2, 3]