dbcve.org
Bus Reservation SystemApplication · Phpjabbers

CVE-2023-53877

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-15
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
Public exploit 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
Bus Reservation System 1.1 contains a SQL injection vulnerability in the pickup_id parameter that allows attackers to manipulate database queries. Attackers can exploit boolean-based, error-based, and time-based blind SQL injection techniques to steal information from 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

Bus Reservation System 1.1 suffers from a critical SQL injection vulnerability in the pickup_id parameter. Attackers can inject malicious SQL statements through this input, enabling boolean-based, error-based, and time-based blind SQL injection attacks to extract sensitive data from the backend database.

MitigationReplace dynamic SQL queries with parameterized queries or prepared statements, and implement proper input validation on the pickup_id parameter and all user-supplied inputs.

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
Bus Reservation SystemApplication
Affected:= 1.1

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. Confirm the exact version of Phpjabbers Bus Reservation System
    Locate the software version in the application admin panel, footer, or in the source files (typically in version.php, README, or config files within the installation directory)
    Affected if The installed version is exactly 1.1 (version 1.1 is the only affected version)
  2. Identify if the pickup_id parameter is in use
    Search the application source code for occurrences of 'pickup_id' in PHP files, particularly in booking, reservation, or search-related controllers and models
    Affected if The application code contains a pickup_id parameter handling user input in SQL queries without parameterization
  3. Check for direct SQL query usage with pickup_id
    Examine PHP files handling bus reservation requests for SQL queries that include the pickup_id variable directly in the query string (look for patterns like 'SELECT ... WHERE pickup_id=' . $_POST['pickup_id'] or similar)
    Affected if Dynamic SQL queries concatenate or embed the pickup_id parameter directly into query strings
  4. Review web application firewall (WAF) or logging for pickup_id injection attempts
    Check web server access logs, WAF logs, or application logs for suspicious patterns in pickup_id parameter values such as SQL keywords (UNION, SELECT, SLEEP, BENCHMARK) or unusual characters
    Affected if Logs show successful or attempted SQL injection payloads through the pickup_id parameter indicating active exploitation
  5. Inspect database user permissions
    Query the database to determine what permissions the application database user has (whether it has access to sensitive tables like users, or permissions to read/write files)
    Affected if The database user has excessive privileges beyond what is required, which could be exploited if SQL injection is present

You are affected if you are running exactly version 1.1 of Phpjabbers Bus Reservation System and the application processes user input through a pickup_id parameter in SQL queries without using parameterized queries or prepared statements.

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 or prepared statements, and implement proper input validation on the pickup_id parameter and all user-supplied inputs.

Fix this in Bus Reservation System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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