CVE-2025-14192
BaseFortify
Publication date: 2025-12-07
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 |
|---|---|---|
| rashmindungrani | online-banking | * |
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?
This vulnerability is a SQL injection found in the RashminDungrani online-banking application, specifically in the /site/dist/auth_login.php file. By manipulating the 'Username' argument, an attacker can inject malicious SQL code. The attack can be performed remotely, and the exploit has been publicly disclosed.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to execute unauthorized SQL commands on the database, potentially leading to unauthorized access, data leakage, data modification, or disruption of service in the online banking system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by identifying the presence of the vulnerable endpoint `/site/dist/auth_login.php` on your system or network. One method is to use Google dorking with the query `inurl:site/dist/auth_login.php` to find exposed instances. Additionally, testing for SQL injection by manipulating the 'Username' parameter in requests to this endpoint can help detect the vulnerability. Specific commands are not provided, but using tools like curl or sqlmap targeting the 'Username' parameter in auth_login.php could be effective. [3]
What immediate steps should I take to mitigate this vulnerability?
No known patches or countermeasures currently exist for this vulnerability, and the vendor has not responded to notifications. Immediate mitigation steps include restricting access to the vulnerable endpoint, implementing web application firewalls (WAF) to detect and block SQL injection attempts, and monitoring for suspicious activity targeting the auth_login.php file. Long term, refactoring the code to use parameterized queries or prepared statements to handle user inputs safely is necessary. [3, 1]