CVE-2025-7830
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-7830 is a critical SQL injection vulnerability in the Church Donation System version 1.0, specifically in the /reg.php file. It occurs because the 'mobile' 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, or full system compromise. 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 tampering, deletion, and exposure of confidential information. It can also result in service disruption or full system compromise, severely impacting 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 monitoring for suspicious SQL injection attempts targeting the /reg.php file, specifically the 'mobile' parameter. You can use web server logs or intrusion detection systems to look for unusual input patterns or SQL syntax in requests. Additionally, Google dorking with queries like 'inurl:reg.php' can help identify exposed vulnerable endpoints. For active testing, tools like sqlmap can be used to test the /reg.php endpoint with the 'mobile' parameter for SQL injection. Example command: sqlmap -u "http://target.com/reg.php?mobile=123" --batch --risk=3 --level=5 [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements (parameterized queries) to ensure user inputs like 'mobile' are treated as data, not executable SQL code. Additionally, apply strict input validation and filtering to allow only expected formats for the 'mobile' parameter. Reduce database user privileges by avoiding high-privilege accounts for routine operations. If possible, replace the affected software with a non-vulnerable alternative. These measures will help prevent exploitation and limit potential damage. [2]