CVE-2025-7829
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-7829 is a critical SQL injection vulnerability in the Church Donation System version 1.0, specifically in the /login.php file. It occurs because the 'username' parameter in the login request is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This flaw enables unauthorized manipulation of SQL queries, potentially giving attackers access to the database without authentication. [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 control over the affected system. It can also cause service disruption. Since it can be exploited remotely without authentication, it 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 /login.php endpoint for SQL injection on the 'username' parameter. You can use tools like sqlmap to automate detection. For example, a command using sqlmap could be: sqlmap -u "http://target/CHURCH_DONATION_SYSTEM/cman/login.php" --data="username=123&password=123&login=Login" -p username --technique=BEUSTQ Additionally, Google dorking can help identify vulnerable targets by searching for "inurl:login.php" to find instances of the affected system. Manual testing can include injecting payloads such as: - Boolean-based blind: username=-1594' OR 2594=2594 # - Time-based blind: username=123' AND (SELECT SLEEP(5))-- Monitoring network traffic for suspicious POST requests to /login.php with unusual input patterns may also help detect exploitation attempts. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1. Replace the affected software with a secure alternative if possible. 2. Apply input validation and filtering on the 'username' parameter to ensure only expected input is accepted. 3. Use prepared statements with parameter binding in the code to prevent SQL injection. 4. Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts such as 'root' or 'admin' for routine operations. Since no official patches or countermeasures are documented, these steps are critical to reduce risk until a secure version or patch is available. [1, 3, 2]