dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-55740

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Nur-Alam39 bus-ticket (no released versions; latest commit 459cabdbeb99c00225b26e46e3c2c30ae1de7bad) contains an unauthenticated SQL injection vulnerability in bus_info.php. The busid parameter received via HTTP POST is concatenated directly into a MySQL query (select * from bus_info where id=) without sanitization, escaping, or parameterization, and in a numeric (unquoted) context.

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

The Nur-Alalam39 bus-ticket application has an unauthenticated SQL injection vulnerability in bus_info.php where the busid parameter from HTTP POST is directly concatenated into a MySQL query in a numeric (unquoted) context without any sanitization, escaping, or parameterization. An attacker can inject arbitrary SQL using UNION-based payloads to exfiltrate data from the database.

MitigationReplace the vulnerable mysqli_query() call with prepared statements using mysqli_prepare() and mysqli_stmt_bind_param() to properly type-bind the busid parameter, ensuring user input is never concatenated into the query string.

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
High
Integrity
High
Availability
High

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

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. Locate the vulnerable PHP file
    Search the web root directory for the file 'bus_info.php' using: find /var/www -name 'bus_info.php' 2>/dev/null or locate bus_info.php
    Affected if If the file exists in the application directory structure
  2. Inspect the SQL query for direct parameter concatenation
    Open bus_info.php and examine the mysqli_query() call. Look for patterns where the busid POST parameter is directly inserted into the query string without any escaping, sanitization, or parameter binding. Search for $_POST['busid'] or similar variable placement inside the query string.
    Affected if If the code shows $_POST['busid'] or similar user input directly concatenated into the query without mysqli_prepare() and bind_param()
  3. Verify the vulnerable numeric context
    Check if the busid parameter is used in a numeric (unquoted) context in the WHERE clause, such as: WHERE busid = $_POST['busid'] or WHERE busid = $busid without quotes around the value
    Affected if If the busid value appears unquoted in the SQL WHERE clause (e.g., WHERE busid = $busid rather than WHERE busid = '$busid')
  4. Confirm POST method handling of busid
    Search the file for $_POST['busid'] and verify it is received and used directly in the query without any sanitization functions like mysqli_real_escape_string, intval, or filter_var
    Affected if If $_POST['busid'] is processed and inserted into the query without validation functions like intval(), mysqli_real_escape_string(), or prepared statements

You are affected if bus_info.php exists in your deployment and contains direct concatenation of the POST busid parameter into an unquoted numeric SQL query without prepared statements or input 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace the vulnerable mysqli_query() call with prepared statements using mysqli_prepare() and mysqli_stmt_bind_param() to properly type-bind the busid parameter, ensuring user input is never concatenated into the query string.

Recommended fix High confidence
  1. Open bus_info.php and locate the SQL query that uses the $busid POST parameter directly.
  2. Replace the direct concatenation with a prepared statement using mysqli_prepare, e.g., $stmt = $mysqli->prepare('SELECT * FROM bus_info WHERE id = ?'); $stmt->bind_param('i', $busid); $stmt->execute();
  3. Validate that $busid is an integer (e.g., using intval) before binding to ensure proper type handling.
  4. Test the endpoint with typical input to confirm the query works correctly.
  5. Change the database connection credentials from the root account with an empty password to a dedicated user with minimal privileges and a strong password.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-55740 — 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-2026-55740 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