CVE-2025-13276VulnerabilityPublished 17 Nov 2025

CVE-2025-13276: g33kyrash Online-Banking-System · SQL Injection

Affects g33kyrash Online-Banking-SystemSource CVE Database V5

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.3% chance of exploitation in 30 days – higher than 25% 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 17 Nov 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

AI-suggested

European organizations should immediately implement rigorous input validation and sanitization on all user-supplied data, especially the Username parameter in the affected system. Employ parameterized queries or prepared statements to prevent SQL injection attacks. Conduct thorough code reviews focusing on database interaction points within the /index.php file and related components. Monitor network traffic and application logs for unusual SQL queries or access patterns indicative of exploitation attempts. Deploy web application firewalls (WAFs) with rules specifically designed to detect and block SQL injection payloads targeting this vulnerability. Engage with the vendor or development team to obtain patches or updates as soon as they become available, and apply them promptly. Given the rolling release model, establish continuous integration and deployment pipelines that include automated security testing for SQL injection vulnerabilities. Train development and security teams on secure coding practices and incident response procedures tailored to banking applications. Finally, prepare incident response plans to quickly contain and remediate any exploitation attempts.

Description

A vulnerability was detected in g33kyrash Online-Banking-System up to 12dbfa690e5af649fb72d2e5d3674e88d6743455. This vulnerability affects unknown code of the file /index.php. The manipulation of the argument Username results in sql injection. It is possible to launch the attack remotely. The exploit is now public and may be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available.

Impact

For European organizations, particularly banks and financial service providers using the g33kyrash Online-Banking-System, this vulnerability could lead to unauthorized disclosure of sensitive customer data, including personal and financial information, violating GDPR requirements. Integrity of transaction records could be compromised, enabling fraudulent activities or financial manipulation. Availability impacts, while partial, could disrupt online banking services, damaging customer trust and causing financial losses. The remote, unauthenticated nature of the exploit increases the likelihood of attacks, potentially targeting high-value European financial institutions. The public availability of an exploit further elevates the risk of widespread exploitation. Given Europe's strong regulatory environment and the critical nature of banking infrastructure, exploitation could result in severe legal, financial, and reputational consequences. Organizations may also face increased scrutiny from regulators and customers if breaches occur due to this vulnerability.

Summary

CVE-2025-13276 is a SQL injection vulnerability identified in the g33kyrash Online-Banking-System, specifically within the /index.php file where the Username parameter is improperly sanitized. This allows an unauthenticated remote attacker to inject malicious SQL code, potentially manipulating the backend database. The vulnerability is present in the rolling release version identified by the commit hash 12dbfa690e5af649fb72d2e5d3674e88d6743455, with no fixed version publicly disclosed yet. The attack vector requires no user interaction or privileges, making it highly accessible to attackers. The CVSS 4.0 vector string (AV:N/AC:L/AT:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P) indicates network attack vector, low attack complexity, no authentication or user interaction, and partial impacts on confidentiality, integrity, and availability. The vulnerability could allow attackers to extract sensitive banking data, modify records, or disrupt services. Although no exploits are currently reported in the wild, the availability of a public exploit increases the urgency for mitigation. The rolling release nature of the software complicates patch management, requiring continuous vigilance. This vulnerability poses a significant risk to financial institutions relying on this system, especially in Europe where online banking is prevalent and data protection regulations are stringent.

References

Community reviews

Loading reviews…