CVE-2025-9305VulnerabilityPublished 21 Aug 2025

CVE-2025-9305: SourceCodester Online Bank Management System · SQL Injection

Affects SourceCodester Online Bank Management SystemSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 4.0 base score

6.9Medium

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

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

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to 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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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 21 Aug 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 26 Oct 2026.

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 Bank Management System	Affected =1.0	Fixed in–

AI-suggested

Organizations should immediately audit their deployment of SourceCodester Online Bank Management System version 1.0 to identify affected instances. As no official patches are currently available, it is critical to implement compensating controls such as: 1) Employing Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the 'ID' parameter in /bank/mnotice.php; 2) Restricting external access to the affected application or segmenting the network to limit exposure; 3) Conducting thorough input validation and sanitization on all user-supplied parameters, especially 'ID', within the application code if source code access and modifications are possible; 4) Monitoring logs for suspicious database query patterns or repeated failed attempts indicative of injection attempts; 5) Planning for an urgent update or migration to a patched version once available from the vendor; 6) Educating security teams to prioritize this vulnerability in their threat detection and incident response workflows.

Description

A security vulnerability has been detected in SourceCodester Online Bank Management System 1.0. The affected element is an unknown function of the file /bank/mnotice.php. The manipulation of the argument ID leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may be used.

Impact

For European organizations using the SourceCodester Online Bank Management System 1.0, this vulnerability poses a substantial risk. Successful exploitation could lead to unauthorized disclosure of sensitive customer financial information, manipulation of transaction records, or disruption of banking services. This could result in financial losses, regulatory penalties under GDPR due to data breaches, and reputational damage. The remote and unauthenticated nature of the attack increases the likelihood of exploitation, especially if the system is exposed to the internet. Given the critical role of banking infrastructure in Europe’s economy, any compromise could have cascading effects on trust and operational continuity. Furthermore, attackers could leverage this vulnerability as a foothold for further lateral movement within the affected organizations’ networks.

Summary

CVE-2025-9305 is a SQL Injection vulnerability identified in version 1.0 of the SourceCodester Online Bank Management System, specifically within an unspecified function in the /bank/mnotice.php file. The vulnerability arises due to improper sanitization or validation of the 'ID' parameter, which can be manipulated remotely without any authentication or user interaction. This allows an attacker to inject malicious SQL queries directly into the backend database. Exploitation of this flaw can lead to unauthorized data access, modification, or deletion, potentially compromising the confidentiality, integrity, and availability of sensitive banking data. The vulnerability has a CVSS 4.0 base score of 6.9, indicating a medium severity level. The attack vector is network-based (remote), requires no privileges or user interaction, and the exploitability is rated as partially functional (E:P). Although no public exploits are currently known in the wild, the public disclosure of the vulnerability increases the risk of exploitation. The lack of available patches or mitigations from the vendor at this time further elevates the threat. Given the critical nature of banking systems, even a medium severity SQL injection can have significant consequences if leveraged by attackers to access customer financial data or disrupt banking operations.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Aug 2025, 15:33 UTC

Technical details

References

Community reviews

Related threats