CVE-2025-11358VulnerabilityPublished 7 Oct 2025

CVE-2025-11358: 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 'ID' parameter in /removeuser.php to prevent SQL injection. 2. Refactor the code to use parameterized queries or prepared statements instead of dynamic SQL concatenation. 3. Restrict access to the /removeuser.php endpoint using network segmentation, firewalls, or application-level access controls to limit exposure. 4. Monitor logs for unusual or suspicious requests targeting the 'ID' parameter or the /removeuser.php script. 5. If possible, upgrade to a patched version of the software once available or apply vendor-provided patches. 6. Conduct a thorough security audit of the entire application to identify and remediate other potential injection points. 7. Educate developers on secure coding practices to prevent similar vulnerabilities in future releases. 8. Employ Web Application Firewalls (WAFs) with SQL injection detection rules as an interim protective measure. 9. Regularly back up databases and ensure recovery procedures are tested to mitigate data loss in case of exploitation.

Description

A weakness has been identified in code-projects Simple Banking System 1.0. Impacted is an unknown function of the file /removeuser.php. Executing manipulation of the argument ID can lead to sql injection. The attack may be launched remotely. The exploit has been made available to the public and could be exploited.

Impact

For European organizations, especially those in the financial sector using the Simple Banking System 1.0, this vulnerability poses a risk of unauthorized access to sensitive customer data and potential manipulation or deletion of user records. Such breaches could lead to financial fraud, regulatory non-compliance (e.g., GDPR violations), reputational damage, and operational disruptions. The ability to remotely exploit the vulnerability without authentication increases the attack surface, potentially allowing attackers to compromise multiple systems if the software is widely deployed. Even though the CVSS score is medium, the critical nature of banking data elevates the practical impact. Organizations may face legal and financial penalties if customer data confidentiality or integrity is compromised. Additionally, attackers could leverage this vulnerability as a foothold for further network penetration or lateral movement within an organization's infrastructure.

Summary

CVE-2025-11358 identifies a SQL injection vulnerability in the Simple Banking System 1.0 developed by code-projects, specifically in the /removeuser.php script. The vulnerability stems from insufficient input validation or sanitization of the 'ID' parameter, which is used in SQL queries to remove users. An attacker can remotely manipulate this parameter to inject arbitrary SQL commands, potentially bypassing authentication or authorization controls, and executing unauthorized database operations. The vulnerability does not require user interaction or elevated privileges, increasing its risk profile. The CVSS 4.0 base score is 5.3 (medium), reflecting network attack vector, low complexity, no privileges required, and no user interaction. The impact on confidentiality, integrity, and availability is limited but present, as attackers can potentially access or modify user data or disrupt user removal functionality. Although no active exploitation has been reported, the public availability of exploit code increases the likelihood of attacks. The lack of official patches or mitigations from the vendor necessitates immediate defensive measures by users of this software. This vulnerability is critical for banking systems where data integrity and confidentiality are paramount, and unauthorized user removal or data manipulation could have severe consequences.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Oct 2025, 08:22 UTC

Technical details

References

Community reviews

Related threats