CVE-2025-14645
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 exists in the Student File Management System 1.0, specifically in the /admin/delete_user.php file. It involves the manipulation of the user_id argument, which leads to an SQL injection vulnerability. This means an attacker can remotely inject malicious SQL code through the user_id parameter to manipulate the database.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to remotely execute SQL injection attacks, potentially leading to unauthorized access, modification, or deletion of data within the system. This can compromise the integrity, confidentiality, and availability of the data managed by the Student File Management System.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not explicitly discuss the impact of this SQL injection vulnerability on compliance with common standards and regulations such as GDPR or HIPAA. However, given that the vulnerability allows unauthorized access, data leakage, and data tampering, it could potentially lead to violations of data protection requirements under such regulations by compromising confidentiality and integrity of sensitive data. Specific compliance implications are not detailed in the available information. [1, 3, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring POST requests to the /admin/delete_user.php endpoint, specifically looking for the user_id parameter being manipulated with SQL injection payloads. Automated tools like sqlmap can be used to identify the injection point and database backend. Example commands include using sqlmap to test the endpoint: sqlmap -u "http://target/StudentFileManagementSystem_PHP/SFMS/admin/delete_user.php" --data="user_id=1" --risk=3 --level=5. Additionally, manual testing with payloads such as 'user_id=539' AND 4740=4740 AND 'SONv'='SONv' or time-based injections like 'user_id=539' AND SLEEP(5) AND 'PpyU'='PpyU' can help confirm the vulnerability. [1, 4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the user_id parameter, and minimizing database user privileges by avoiding high-privilege accounts for routine operations. If possible, replace the affected software with an alternative product. Since no known countermeasures are documented, applying these best practices is critical to protect system integrity and data confidentiality. [1, 4]