CVE-2025-13276CWE-74CWE-89sql-injection

CVE-2025-13276

High · published November 17, 2025

CVSS v3.1
7.3
EPSS
0%
Percentile
24.6
In the wild
Unconfirmed
What it is

⚠️ A sneaky SQL injection vulnerability lurks in the g33kyrash Online-Banking-System's /index.php file, and it can be exploited remotely! Think of this as a restaurant where an attacker can shout their order directly to the kitchen without anyone checking the menu first — they could ask for anything! If the chef isn’t careful, the wrong dish could be served, causing chaos in the dining room. An attacker could manipulate the Username argument to execute arbitrary SQL commands, potentially exposing or altering sensitive data. While it’s not an immediate disaster, it opens the door to unauthorized access and data breaches, which can be quite damaging for users. This kind of vulnerability is like leaving the backdoor of your online bank slightly ajar — inviting trouble!

Put simply

Think of this as a restaurant where an attacker can shout their order directly to the kitchen without anyone checking the menu first — they could ask for anything! If the chef isn’t careful, the wrong dish could be served, causing chaos in the dining room. This SQL injection vulnerability arises from inadequate input validation in the /index.php file, allowing attackers to inject malicious SQL queries by simply altering the Username parameter. This means they could gain access to sensitive information stored in the database.

What to do

An attacker could manipulate the Username argument to execute arbitrary SQL commands, potentially exposing or altering sensitive data. While it’s not an immediate disaster, it opens the door to unauthorized access and data breaches, which can be quite damaging for users. This kind of vulnerability is like leaving the backdoor of your online bank slightly ajar — inviting trouble! Developers should immediately audit the input validation for the Username parameter in /index.php. Implement prepared statements and parameterized queries to mitigate the risk of injection. Since the software uses rolling releases, keep an eye out for updates that address this vulnerability. You've got this! With these steps, you can secure your banking system and keep your users safe! 🛡️

The record
Technical detail
CVSS v3.1
7.3 · HIGH
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
CVSS v4.0
Not supplied
EPSS
0.00328 · 24.6th percentile
Weaknesses
CWE-74 · Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection'); CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Published
2025-11-17T16:15Z
References (4)
EPSS history
Timeline
  • 17 NOV 11:02Z
    g33kyrash Online-Banking-System index.php sql injection
    cvelistv5