CVE-2025-14620
BaseFortify
Publication date: 2025-12-13
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 |
|---|---|---|
| fabian | student_file_management_system | 1.0 |
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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized access, data leakage, and data tampering due to SQL injection in the Student File Management System. This compromises confidentiality, integrity, and availability of sensitive data, which can lead to non-compliance with data protection standards and regulations such as GDPR and HIPAA that require safeguarding personal and sensitive information. Immediate remediation is critical to maintain data integrity and protect user privacy. [1, 2, 3, 5]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'username' parameter in the /admin/login_query.php file for SQL injection. Tools like sqlmap can be used to automate detection and enumeration of databases. Example commands include using sqlmap with the URL targeting the vulnerable parameter, e.g., `sqlmap -u "http://target/admin/login_query.php?username=admin" --batch`. Additionally, manual testing with payloads such as `admin' AND 1=1--` (boolean-based), `admin' AND SLEEP(5)--` (time-based), or UNION-based queries can confirm the vulnerability. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL code from user input, enforcing strict input validation and filtering on the 'username' parameter, and minimizing database user privileges by avoiding use of high-privilege accounts for routine operations. Since no known mitigations or countermeasures are documented, replacing the affected software with an alternative product is also suggested to fully remediate the issue. [1, 2]
Can you explain this vulnerability to me?
This vulnerability exists in the Student File Management System 1.0, specifically in the /admin/login_query.php file. It allows an attacker to manipulate the 'Username' argument to perform SQL injection, which means the attacker can inject malicious SQL code into the system's database queries. This can be exploited remotely and the exploit has been publicly disclosed.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to execute arbitrary SQL commands on the database, potentially leading to unauthorized access, data leakage, data modification, or deletion. This can compromise the confidentiality, integrity, and availability of the system's data.