CVE-2025-14221VulnerabilityPublished 8 Dec 2025

CVE-2025-14221: SourceCodester Online Banking System · Cross Site Scripting

Affects SourceCodester Online Banking SystemSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
SourceCodester Online Banking System	Affected =1.0	Fixed in–

AI-suggested

1. Immediately implement strict input validation and output encoding on the First Name and Last Name parameters to neutralize malicious scripts. 2. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. 3. Educate users and staff about phishing risks and the dangers of clicking on suspicious links, especially those related to banking services. 4. Monitor web application logs for unusual requests targeting the /?page=user endpoint with suspicious input patterns. 5. If patching is not yet available, consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block XSS payloads targeting the vulnerable parameters. 6. Conduct regular security assessments and penetration testing focused on input validation and XSS vulnerabilities. 7. Coordinate with SourceCodester for official patches or updates and plan for timely deployment once released. 8. Implement multi-factor authentication (MFA) to reduce the impact of stolen credentials or session hijacking.

Description

A vulnerability was detected in SourceCodester Online Banking System 1.0. This impacts an unknown function of the file /?page=user. The manipulation of the argument First Name/Last Name results in cross site scripting. The attack can be launched remotely. The exploit is now public and may be used.

Impact

For European organizations, this vulnerability poses a moderate risk primarily to the confidentiality and integrity of user sessions within the affected online banking system. Successful exploitation could allow attackers to hijack user sessions, steal sensitive banking credentials, or conduct fraudulent transactions under the guise of legitimate users. This can lead to financial losses, reputational damage, and regulatory penalties under GDPR due to compromised personal data. The attack requires user interaction, which somewhat limits mass exploitation but targeted phishing campaigns could be effective. The impact is particularly significant for banks and financial institutions using SourceCodester Online Banking System 1.0 or derivative products. Given the critical nature of banking services, even moderate vulnerabilities can have outsized consequences. Additionally, the public availability of an exploit increases the urgency for European entities to address this issue promptly to prevent exploitation.

Summary

CVE-2025-14221 is a cross-site scripting vulnerability identified in SourceCodester Online Banking System version 1.0. The vulnerability arises from improper sanitization of user-supplied input in the First Name and Last Name parameters on the /?page=user endpoint. Attackers can craft malicious payloads that, when injected into these parameters, execute arbitrary JavaScript code in the context of authenticated users' browsers. This type of vulnerability is classified as reflected XSS, as the malicious script is reflected off the web server in the response. The attack vector is remote and does not require prior authentication, but successful exploitation depends on tricking a user into clicking a malicious link or visiting a compromised page, thus requiring user interaction. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:L), user interaction required (UI:P), and low impact on confidentiality and integrity (VC:N, VI:L) with no impact on availability (VA:N). The vulnerability can be leveraged to steal session cookies, perform actions on behalf of the user, or redirect users to malicious sites, potentially leading to account compromise or data theft. Although no active exploits are reported in the wild, the availability of a public exploit increases the likelihood of exploitation attempts. The lack of official patches necessitates immediate mitigation efforts by affected organizations.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Dec 2025, 07:11 UTC

Technical details

References

Community reviews

Related threats