CVE-2025-14662
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-14

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability was found in code-projects Student File Management System 1.0. This affects an unknown part of the file /admin/update_user.php of the component Update User Page. Performing manipulation results in cross site scripting. The attack may be initiated remotely. The exploit has been made public and could be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-14
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2025-12-14
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
fabian student_file_management_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
CWE-94 The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2025-14662 is a stored Cross-Site Scripting (XSS) vulnerability in the Student File Management System version 1.0, specifically in the update_user.php file. The vulnerability arises because the system does not properly validate, sanitize, or escape user input in the firstname and lastname fields submitted via POST requests. Malicious scripts submitted in these fields are stored directly in the database and later rendered in web pages without neutralization, allowing attackers to execute arbitrary JavaScript in the context of users viewing the affected pages. This can lead to unauthorized actions such as account hijacking. [1, 3]


How can this vulnerability impact me? :

This vulnerability can allow remote attackers to execute arbitrary scripts in the context of an administrator or victim user. This can lead to account hijacking, unauthorized actions, and compromise of data integrity. Since the malicious payloads are stored and executed when the affected pages are viewed, attackers can persistently exploit the system to manipulate user sessions or steal sensitive information. [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 checking for the presence of the vulnerable update_user.php page, especially by searching for the URL path /admin/update_user.php. You can use Google dorking with queries like 'inurl:admin/update_user.php' to find exposed instances. Additionally, monitoring POST requests to /admin/update_user.php with suspicious payloads containing HTML or JavaScript tags such as <img src=x onerror=alert(1)> can help detect exploitation attempts. On your system, you can use tools like curl or wget to send crafted POST requests to test if the inputs firstname and lastname are vulnerable to stored XSS. For example, a curl command to test might be: curl -X POST -d "firstname=<img src=x onerror=alert(1)>" -d "lastname=test" http://yourserver/StudentFileManagementSystem_PHP/SFMS/admin/update_user.php. Also, inspecting database entries in the user table for stored malicious scripts can indicate exploitation. [1, 2, 3]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include implementing strict input validation and sanitization on the firstname and lastname fields in the update_user.php script. This involves limiting input length, filtering or escaping special characters such as <, >, ', ", /, and , and allowing only specific character sets like letters, numbers, and underscores. Reject any input that does not conform to these rules. Additionally, properly encode output when displaying these fields to prevent script execution. If possible, replace the affected software with a secure alternative. Applying these measures will help prevent stored XSS attacks and protect system security and data integrity. [1, 3, 2]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart