CVE-2025-14640
BaseFortify
Publication date: 2025-12-14
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-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 found in the Student File Management System 1.0, specifically in the /admin/save_student.php file. Manipulating the 'stud_no' argument can allow an attacker to execute unauthorized SQL commands remotely, potentially compromising the database.
How can this vulnerability impact me? :
The vulnerability can allow remote attackers to perform SQL injection attacks, which may lead to unauthorized access, data leakage, data modification, or disruption of the database and application functionality.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This SQL injection vulnerability can lead to unauthorized access, modification, or disclosure of sensitive student data, impacting the confidentiality, integrity, and availability of the system. Such data breaches can result in non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information. Failure to remediate this vulnerability may expose organizations to legal and regulatory penalties due to compromised data security. [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 identifying HTTP POST requests to the /admin/save_student.php endpoint with the vulnerable parameter 'stud_no'. You can use Google hacking with the query "inurl:admin/save_student.php" to find potentially vulnerable targets. Additionally, tools like sqlmap can be used to test for SQL injection by targeting the 'stud_no' parameter. Example sqlmap command: sqlmap -u "http://target/StudentFileManagementSystem_PHP/SFMS/admin/save_student.php" --data="stud_no=1" --risk=3 --level=5 --batch. Proof-of-concept payloads include boolean-based blind, time-based blind, and UNION query injections on the 'stud_no' parameter. Monitoring for unusual SQL errors or delays in responses when sending crafted payloads can also help detect exploitation attempts. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replace the affected component with an alternative product if possible, as no known countermeasures currently exist. 2) Implement prepared statements with parameter binding to separate SQL code from user input. 3) Apply strict input validation and filtering to ensure inputs conform to expected formats. 4) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. 5) Monitor and block suspicious HTTP POST requests targeting /admin/save_student.php with malicious 'stud_no' parameters. These steps help prevent exploitation and protect system security and data integrity. [1, 3]