CVE-2025-14646
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-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 flaw in the Student File Management System 1.0, specifically in the /admin/delete_student.php file. It occurs due to improper handling of the stud_id argument, allowing an attacker to manipulate SQL queries remotely.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to execute arbitrary SQL commands on the database, potentially leading to unauthorized data access, data modification, or deletion. This can compromise the integrity, confidentiality, and availability of the system's data.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This SQL injection vulnerability allows unauthorized access, modification, and extraction of sensitive student information, which can lead to breaches of confidentiality and data integrity. Such breaches can result in non-compliance with data protection regulations like GDPR and HIPAA, which mandate the protection of personal and sensitive data. Failure to remediate this vulnerability may expose organizations to legal and regulatory penalties due to compromised data security. [1, 2, 4]
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_id' parameter in POST requests to the /admin/delete_student.php endpoint for SQL injection. Automated tools like sqlmap can be used to confirm the vulnerability by enumerating databases. Additionally, Google dorking with the query 'inurl:admin/delete_student.php' can help identify vulnerable targets. Example sqlmap command: sqlmap -u "http://target/admin/delete_student.php" --data="stud_id=1" --risk=3 --level=5 --batch. Manual testing can include injecting payloads such as '75' AND 1=1-- or time-based payloads like '75' AND SLEEP(5)-- into the stud_id parameter to observe abnormal behavior or delays. [2, 4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Enforce strict input validation and filtering to ensure the stud_id parameter conforms to expected formats. 3) Restrict database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. 4) If possible, replace the affected component with an alternative product. These steps help protect system integrity and data confidentiality against exploitation. [1, 2, 4]