CVE-2025-9304
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 weakness has been identified in SourceCodester Online Bank Management System 1.0. Impacted is an unknown function of the file /bank/show.php. Executing manipulation of the argument ID can lead to sql injection. The attack may be performed from a remote location. The exploit has been made available to the public and could be exploited.
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 confidenceSQL injection vulnerability in SourceCodester Online Bank Management System 1.0 allows remote attackers to manipulate the ID parameter in /bank/show.php to inject arbitrary SQL commands, potentially exposing or modifying sensitive banking data.
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.
-
Verify the application is installedCheck your web server for the presence of SourceCodester or Oretnom23 Online Bank Management System files. Look for directories containing 'bank', 'online bank', or similar naming in the web root.Affected if The Online Bank Management System version 1.0 is installed on the server
-
Locate the vulnerable scriptSearch for the file /bank/show.php within the application directory structure on the web server.Affected if The file /bank/show.php exists in the application
-
Examine the show.php code for SQL query handlingOpen /bank/show.php and inspect how the ID parameter is processed. Look for SQL queries that directly incorporate the ID parameter without using prepared statements or parameter binding.Affected if The code contains SQL queries that concatenate or embed the ID parameter directly into the query string
-
Check if the application accepts user input for the ID parameterReview the show.php file to determine if it reads the ID parameter from GET or POST requests (e.g., $_GET['id'] or $_POST['id']) and passes it directly to the database.Affected if The ID parameter is received from user input and used in SQL queries without sanitization or parameterization
-
Test the ID parameter for SQL injection (authorized testing only)If authorized, submit a benign SQL payload such as "1' OR '1'='1" to the ID parameter in /bank/show.php and observe if unexpected data is returned or if the query behavior changes.Affected if The ID parameter reflects SQL injection behavior, returning data that differs from expected queries or producing database errors
A user is affected if the Online Bank Management System version 1.0 is installed and the /bank/show.php file contains SQL queries that handle the ID parameter without prepared statements or input sanitization.
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 dataImplement prepared statements/parameterized queries for all database queries, particularly those accepting user input like the ID parameter in show.php, and apply input validation as a defense-in-depth measure.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9304 — 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-9304 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