CVE-2025-7833
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-7833 is a critical SQL injection vulnerability in version 1.0 of the Church Donation System, specifically in the /members/giving.php file. It occurs because the 'amount' 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 gaining unauthorized access to the database, manipulating data, or causing other harmful effects. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access to sensitive data, data leakage, modification or deletion of data, and potentially full system compromise. Attackers can exploit it remotely without authentication, which may disrupt business operations, compromise data integrity, and expose confidential information. [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/giving.php endpoint for SQL injection via the 'amount' parameter. You can use SQL injection testing tools or manual curl commands to send crafted payloads. For example, using curl to send a boolean-based blind SQL injection payload: curl -X POST -d "amount=1' RLIKE (SELECT (CASE WHEN (7441=7441) THEN 1 ELSE 0x28 END)) AND 'SoKR'='SoKR" http://target/members/giving.php. Additionally, Google dorking with the query inurl:members/giving.php can help locate vulnerable targets. Automated scanners that test for SQL injection on POST parameters can also be used. [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 'amount' parameter to ensure it conforms to expected numeric formats. 3) Minimizing database user privileges by avoiding the use of high-privilege accounts for routine database operations. If possible, replace the affected product with a secure alternative. These steps help protect system security and maintain data integrity. [1, 3, 2]