CVE-2025-14221
BaseFortify
Publication date: 2025-12-08
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 |
|---|---|---|
| sourcecodester | online_banking_system | 1.0 |
| oretnom23 | banking_system | 1.0 |
Helpful Resources
Exploitability
| 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?
This vulnerability exists in the SourceCodester Online Banking System 1.0, specifically in an unknown function of the file /?page=user. It involves manipulation of the First Name or Last Name argument, which leads to a cross-site scripting (XSS) vulnerability. This means an attacker can inject malicious scripts that run in the context of the user's browser. The attack can be launched remotely, and an exploit is publicly available.
How can this vulnerability impact me? :
The vulnerability can allow attackers to execute malicious scripts in the context of users' browsers. This can lead to unauthorized actions such as stealing session cookies, redirecting users to malicious sites, or performing actions on behalf of the user without their consent. Since the attack is remote and the exploit is public, it increases the risk of exploitation.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the user profile update functionality, specifically by attempting to inject JavaScript code into the 'First Name' or 'Last Name' fields via the URL parameter '/?page=user'. Since it is a stored cross-site scripting (XSS) vulnerability, you can try submitting payloads such as <script>alert(1)</script> in these fields and then observe if the script executes when viewing the profile page. There are no specific network commands provided, but manual or automated web application security testing tools (such as Burp Suite or OWASP ZAP) can be used to detect this XSS vulnerability by intercepting and modifying HTTP requests to inject scripts and monitoring responses for script execution. [1, 4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include disabling or restricting access to the vulnerable user profile update functionality, especially for low-privilege users, until a patch or fix is applied. Input validation and proper output encoding should be implemented to neutralize and encode user-supplied data in the 'First Name' and 'Last Name' fields to prevent script injection. Additionally, consider replacing the affected software with an alternative product as no known mitigations or countermeasures have been documented. Monitoring for suspicious activity and educating users about the risk of XSS attacks can also help reduce impact. [4, 1]