dbcve.org
HubbankApplication · Ofofonobsdev

CVE-2024-4308

HIGH · 8.1 CVSS v3.1 Published 2024-04-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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
SQL injection vulnerability in HubBank affecting version 1.0.2. This vulnerability could allow an attacker to send a specially crafted SQL query to the database through different endpoints (/admin/view_users.php?id=1,/admin/viewloan-trans.php?id=1,/admin/view-deposit.php?id=1,/admin/view-domtrans.php?id=1, /admin/delete_cards.php?id=1,/admin/view_cards.php?id=1 and /admin/view_users.php?id=1, id parameter) and retrieve the information stored in the database.

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 HubBank v1.0.2 allows attackers to inject malicious SQL queries through the unprotected 'id' parameter in seven admin endpoints (view_users.php, view_loan-trans.php, view_deposit.php, view_domtrans.php, delete_cards.php, view_cards.php). Successful exploitation enables database information disclosure.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements across all affected endpoints to properly sanitize the id parameter input before executing database queries.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
HubbankApplication
Affected:= 1.0.2

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

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 HubBank installation version
    Locate the HubBank installation directory and check for version indicators such as a version file, header comments in PHP files, or the admin dashboard version display
    Affected if The installed version is 1.0.2 or cannot be determined but the application is HubBank
  2. Identify affected PHP files
    Check the admin directory for the presence of: view_users.php, view_loan-trans.php, view_deposit.php, view_domtrans.php, delete_cards.php, view_cards.php, and verify the seventh endpoint exists
    Affected if Any of these seven affected PHP files are present in the web application directory
  3. Inspect SQL query implementation in affected files
    Open each affected PHP file and locate the SQL query sections that use the 'id' parameter - search for patterns like $_GET['id'] or $_POST['id'] being directly concatenated into SQL statements
    Affected if The 'id' parameter is used directly in SQL queries without prepared statements or parameter binding
  4. Check for input sanitization on the id parameter
    Search the affected files for sanitization functions such as mysqli_real_escape_string, htmlspecialchars, or input validation before using the id parameter in queries
    Affected if No input sanitization or validation is performed on the 'id' parameter before executing database queries
  5. Verify admin endpoint accessibility
    Confirm the affected files are accessible via the web server without authentication requirements or with weak authentication
    Affected if The affected endpoints are accessible to unauthenticated or low-privilege users

A user is affected if they have HubBank v1.0.2 installed with any of the seven vulnerable PHP files present and the 'id' parameter is used in SQL queries without prepared statements or sanitization.

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 queries with parameterized queries/prepared statements across all affected endpoints to properly sanitize the id parameter input before executing database queries.

Fix this in Hubbank 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-2024-4308 — 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-2024-4308 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