Cross-Site Scripting (XSS) in SourceCodester Online Banking System (CVE-2025-14221)
Summary
Cross-site scripting in SourceCodester Online Banking System (CVE-2025-14221). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-14221 has been found in SourceCodester Online Banking System.
Risk of unauthorized operations or information disclosure. CVSS score: 3.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "SourceCodester Online Banking System CVE-2025-14221" on the vendor's site.
CVE-2025-14221 (SourceCodester Online Banking System) — CWE-79 / CVSS v3 3.5
Attack vector: remote (network-reachable)
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in SourceCodester Online Banking System.
Check the vendor advisory for the affected versions of SourceCodester Online Banking System.
Severity: Low (CVSS 3.5/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで SourceCodester Online Banking System を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory cna@vuldb.com
- advisory cna@vuldb.com
- exploit cna@vuldb.com
- web cna@vuldb.com
- web cna@vuldb.com