dbcve.org
InjectionWeakness · CWE-74

CVE-2025-13276

HIGH · 7.3 CVSS v3.1 Published 2025-11-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in the Username parameter of /index.php in g33kyrash Online-Banking-System allows remote attackers to manipulate SQL queries, potentially enabling authentication bypass, data exfiltration, or database compromise.

MitigationReplace dynamic SQL query construction with parameterized queries (prepared statements) for all user inputs, particularly the Username parameter. Implement input validation and consider deploying a WAF as an interim control.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm g33kyrash Online-Banking-System is installed
    Search the webroot for files containing 'Online-Banking-System', 'g33kyrash', or the application name in HTML title/meta tags. Check for the presence of /index.php in the web directory.
    Affected if The application g33kyrash Online-Banking-System is present on the server
  2. Identify the installed version
    Check for version information in source files (e.g., version.php, README, changelog), or in the index.php header comments. Compare the found version against any documented affected version ranges.
    Affected if The installed version falls within an affected range (if such ranges become known)
  3. Inspect the login handling code in /index.php
    Open /index.php in a text editor or use 'grep' to search for SQL query construction patterns. Look for dynamic string concatenation involving the Username parameter, such as 'SELECT ... WHERE username = ' . $_POST['username'] or similar patterns.
    Affected if The code constructs SQL queries using string concatenation with user-supplied input from the Username parameter without using prepared statements
  4. Verify if parameterized queries are implemented
    Search the codebase for PDO prepared statements, mysqli_prepare, or other parameterized query mechanisms. Specifically check the authentication logic in /index.php for proper use of bound parameters.
    Affected if Parameterized queries are NOT used for the Username parameter in the login SQL query
  5. Test the Username parameter for SQL injection behavior
    If permitted by policy, send a test payload such as "admin' OR '1'='1" to the Username field in /index.php and observe if the application returns unexpected authentication results or SQL errors.
    Affected if The application exhibits SQL injection behavior (authentication bypass or SQL error messages) when special characters are submitted in the Username field

A user is affected if g33kyrash Online-Banking-System is installed, /index.php uses dynamic SQL construction with the Username parameter without prepared statements, and the application accepts user input through that parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL query construction with parameterized queries (prepared statements) for all user inputs, particularly the Username parameter. Implement input validation and consider deploying a WAF as an interim control.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13276 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13276 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data