Skip to main content
CVE-2025-11608VulnerabilityPublished Updated

CVE-2025-11608: code-projects E-Banking System · SQL Injection

Affects code-projects E-Banking SystemSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 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 40% 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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
code-projects E-Banking SystemAffected
  • =1.0
Fixed in–

AI-suggested

Organizations should immediately audit their deployment of code-projects E-Banking System version 1.0 to identify affected instances. Until a vendor patch is available, implement strict input validation and sanitization on all user-supplied data, especially the username and password fields in /register.php. Employ parameterized queries or prepared statements to prevent SQL injection. Use Web Application Firewalls (WAFs) with rules designed to detect and block SQL injection attempts targeting the vulnerable endpoint. Conduct thorough code reviews and penetration testing focused on input handling and authentication modules. Monitor logs for unusual database queries or failed login attempts indicative of exploitation attempts. Segregate and limit database privileges for the application to minimize potential damage. Prepare incident response plans specific to SQL injection attacks. Engage with the vendor for timely patch releases and apply updates promptly once available. Additionally, raise awareness among development teams about secure coding practices to prevent similar vulnerabilities.

Description

A security vulnerability has been detected in code-projects E-Banking System 1.0. This affects an unknown function of the file /register.php of the component POST Parameter Handler. The manipulation of the argument username/password leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may be used.

References

Community reviews

Loading reviews…