CVE-2025-14619
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
Can you explain this vulnerability to me?
This vulnerability exists in the Student File Management System 1.0, specifically in the login_query.php file. It allows an attacker to perform SQL injection by manipulating the 'stud_no' argument. This means an attacker can inject malicious SQL code remotely to potentially access or alter the database.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to remotely execute SQL injection attacks, which may lead to unauthorized access, modification, or deletion of data within the system's database. This can compromise the confidentiality, integrity, and availability of the data managed by the system.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in the Student File Management System allows unauthorized access, data leakage, and data tampering, which can lead to breaches of sensitive personal or health information. Such breaches can result in non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal data against unauthorized access and ensuring data integrity. Therefore, exploitation of this vulnerability could cause violations of these standards and regulations. [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 'stud_no' parameter in the login_query.php file for SQL injection flaws. You can use tools like sqlmap to automate detection. Example sqlmap command: sqlmap -u "http://targetsite/login_query.php" --data="stud_no=123&password=abc" -p stud_no --batch --dbs. Additionally, manual testing with payloads such as 'id=r350nfbw' AND 4740=4740 AND 'SONv'='SONv' (Boolean-based blind SQLi) or 'id=r350nfbw' AND SLEEP(5) AND 'PpyU'='PpyU' (time-based blind SQLi) can be used to confirm the vulnerability. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to separate SQL code from user input. 2) Implement strict input validation and filtering to ensure inputs conform to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts like root or admin for routine operations. These measures help prevent exploitation of the SQL injection vulnerability in the 'stud_no' parameter. [2]