CVE-2025-11357VulnerabilityPublished 7 Oct 2025

CVE-2025-11357: code-projects Simple Banking System · SQL Injection

Affects code-projects Simple Banking SystemSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 26% 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: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: Low
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: 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: 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 7 Oct 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
code-projects Simple Banking System	Affected =1.0	Fixed in–

AI-suggested

1. Immediately implement input validation and sanitization on the 'Name' parameter in /createuser.php to block malicious SQL payloads. 2. Refactor the application code to use parameterized queries or prepared statements to prevent SQL injection. 3. Restrict database user permissions to the minimum necessary, avoiding use of highly privileged accounts for application access. 4. Employ Web Application Firewalls (WAFs) with rules designed to detect and block SQL injection attempts targeting this endpoint. 5. Monitor application logs and database activity for unusual queries or access patterns indicative of exploitation attempts. 6. Isolate or limit network exposure of the vulnerable application, restricting access to trusted IP ranges where possible. 7. Engage with the vendor or development community to obtain or develop an official patch or updated version. 8. Conduct security code reviews and penetration testing to identify and remediate similar vulnerabilities elsewhere in the application. 9. Educate developers on secure coding practices to prevent recurrence of injection flaws. 10. Prepare incident response plans to quickly address any detected exploitation.

Description

A security flaw has been discovered in code-projects Simple Banking System 1.0. This issue affects some unknown processing of the file /createuser.php. Performing manipulation of the argument Name results in sql injection. The attack may be initiated remotely. The exploit has been released to the public and may be exploited.

Impact

For European organizations, this vulnerability poses a risk of unauthorized data access and manipulation within banking systems using the affected software. Exploitation could lead to exposure of sensitive customer data, financial fraud, or disruption of banking operations. Even though the severity is medium, the financial sector's high regulatory requirements (e.g., GDPR, PSD2) mean that any data breach could result in significant legal and reputational consequences. The ability to remotely exploit the vulnerability without authentication increases the attack surface, especially for internet-facing banking applications. Organizations relying on this software may face increased risk of targeted attacks or automated scanning by threat actors leveraging the publicly available exploit. Additionally, the lack of an official patch means organizations must implement interim mitigations to reduce exposure. The impact extends beyond direct financial loss to potential erosion of customer trust and regulatory penalties.

Summary

CVE-2025-11357 is a SQL injection vulnerability identified in version 1.0 of the Simple Banking System developed by code-projects. The vulnerability resides in the /createuser.php endpoint, where the 'Name' parameter is improperly sanitized, allowing an attacker to inject malicious SQL commands. This flaw can be exploited remotely without requiring user interaction or elevated privileges, making it accessible to unauthenticated attackers with network access to the application. The SQL injection can lead to unauthorized reading, modification, or deletion of database records, potentially compromising sensitive banking data such as user credentials, account information, or transaction records. The CVSS 4.0 base score of 5.3 (medium severity) reflects that while the attack vector is network-based and requires no user interaction, the impact on confidentiality, integrity, and availability is limited to low levels. No patches or official fixes have been published yet, and although proof-of-concept exploit code is publicly available, there are no confirmed reports of active exploitation in the wild. The vulnerability highlights the critical need for secure coding practices, especially in financial applications where data integrity and confidentiality are paramount.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Oct 2025, 07:37 UTC

Technical details

References

Community reviews

Related threats