CVE-2025-14621
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 can this vulnerability impact me? :
The vulnerability can allow remote attackers to perform SQL injection attacks, potentially leading to unauthorized access, data leakage, data modification, or disruption of the system's database.
Can you explain this vulnerability to me?
This vulnerability exists in the Student File Management System 1.0, specifically in the /admin/update_user.php file. It involves SQL injection through manipulation of the user_id argument, allowing an attacker to execute unauthorized SQL commands remotely.
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 database access, data leakage, and data tampering, it can potentially lead to violations of data protection regulations that require safeguarding personal and sensitive information. Immediate remediation is necessary to protect data integrity and system security, which are critical for compliance. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by testing the 'user_id' parameter in POST requests to /admin/update_user.php for SQL injection payloads. Example payloads include boolean-based blind SQL injection such as `user_id=4' AND 4740=4740 AND 'SONv'='SONv`, time-based blind SQL injection like `user_id=4' AND SLEEP(5) AND 'PpyU'='PpyU`, and UNION-based queries such as `user_id=4' UNION ALL SELECT NULL,NULL,NULL,CONCAT(...)-- -`. You can use tools like curl or sqlmap to send these payloads and observe responses or delays indicating vulnerability. For example, a curl command to test time-based injection might be: curl -X POST -d "user_id=4' AND SLEEP(5) AND 'PpyU'='PpyU" https://yourserver/StudentFileManagementSystem_PHP/SFMS/admin/update_user.php Additionally, Google dorking with queries like `inurl:admin/update_user.php` can help identify vulnerable targets. [1, 3]
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. - Applying strict input validation and filtering to ensure 'user_id' and other inputs conform to expected formats. - Minimizing database user permissions by avoiding elevated privilege accounts for routine operations. - If possible, replacing the affected software with a secure alternative. These actions help prevent SQL injection exploitation and protect data integrity and system security. [1]