CVE-2025-9021
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability was determined in SourceCodester Online Bank Management System up to 1.0. This vulnerability affects unknown code of the file /bank/transfer.php. The manipulation of the argument email leads to sql injection. The attack can be initiated remotely.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA critical SQL injection vulnerability exists in SourceCodester Online Bank Management System 1.0 within the /bank/transfer.php file. The email parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL commands and potentially exfiltrate or manipulate the database.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm application identity and versionIdentify the installed web application. Check for files like readme.txt, about.php, or the main index page that display the application name and version. SourceCodester Online Bank Management System 1.0 may also be listed as Oretnom23 Online Bank Management System.Affected if The application is SourceCodester/Oretnom23 Online Bank Management System version 1.0
-
Locate vulnerable transfer.php fileCheck if the file /bank/transfer.php exists in the webroot. This file handles fund transfer functionality and contains the vulnerable email parameter.Affected if The file /bank/transfer.php exists in the deployed application
-
Inspect email parameter handling in transfer.phpExamine the source code of /bank/transfer.php. Look for SQL queries that incorporate the 'email' parameter without proper sanitization, parameterized queries, or input validation. Search for patterns like $_POST['email'] or $_GET['email'] being concatenated directly into SQL strings.Affected if The email parameter is used in SQL queries without prepared statements, parameter binding, or input sanitization
-
Verify database connectivityConfirm the application connects to a MySQL or MariaDB database. Check configuration files (such as config.php or db.php) for database credentials and connection settings.Affected if The application uses a database and the vulnerable transfer.php file processes user-supplied email data
If the organization runs SourceCodester/Oretnom23 Online Bank Management System version 1.0 with the /bank/transfer.php file present and the email parameter is directly concatenated into SQL queries without prepared statements, the environment is affected by CVE-2025-9021.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace direct string concatenation in SQL queries with parameterized queries (prepared statements) for the email parameter. Implement proper input validation and escaping. Apply principle of least privilege to the database user.
- Consultation6.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,816.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9021 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-9021 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data