CVE-2025-8166
BaseFortify
Publication date: 2025-07-25
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?
This vulnerability is a SQL injection flaw in the login form of the Church Donation System version 1.0, specifically in the 'username' parameter of the /admin/index.php page's HTTP POST request handler. An attacker can manipulate the 'username' input to inject malicious SQL commands, allowing them to bypass authentication and gain unauthorized access to the admin dashboard. The injection techniques confirmed include boolean-based blind and time-based blind SQL injection against a MySQL database. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can severely impact you by allowing an attacker to remotely bypass authentication without any credentials, gaining unauthorized access to the admin dashboard. This compromises the confidentiality, integrity, and availability of the system, potentially leading to data breaches, unauthorized data manipulation, and disruption of services. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /admin/index.php login form's POST parameter "username" for SQL injection using boolean-based blind and time-based blind SQL injection techniques. Example commands include sending crafted POST requests with payloads such as: - Boolean-based blind SQL injection payload: username=-1290' OR 3222=3222#&password=m&login= - Time-based blind SQL injection payload: username=m' AND (SELECT 1548 FROM (SELECT(SLEEP(5)))ujap)-- oydK&password=m&login= These payloads can be sent using tools like curl or automated with sqlmap using a request file. Successful exploitation is indicated by bypassing authentication and gaining access to the dashboard (HTTP 302 redirect to dashboard.php). [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected software with an alternative product, as no known countermeasures or patches are reported. Additionally, restricting access to the /admin/index.php page, implementing web application firewalls (WAF) to detect and block SQL injection attempts, and monitoring for suspicious POST requests targeting the "username" parameter can help reduce risk until a fix is applied. [2]