CVE-2023-53877VulnerabilityPublished 15 Dec 2025

CVE-2023-53877: Phpjabbers Bus Reservation System · SQL Injection

Affects Phpjabbers Bus Reservation SystemSource CVE Database V5

Not known to be exploited · CVSS 9.3 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

9.3Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 38% 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:H/VI:H/VA:L/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: High
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

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: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the vulnerable system. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence 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.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Dec 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

Affected software

Product	Affected	Fixed in
Packagistphpjabbers/bus-reservation-system`pkg:composer/phpjabbers/bus-reservation-system`Other threats	Affected =1.1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Immediate mitigation involves applying vendor-provided patches once available. In the absence of patches, organizations should implement strict input validation on the 'pickup_id' parameter, ensuring only expected numeric or alphanumeric values are accepted. Employing parameterized queries or prepared statements in the application code will prevent SQL injection by separating code from data. Web application firewalls (WAFs) can be configured to detect and block SQL injection payloads targeting this parameter. Regular security testing, including automated scanning and manual penetration testing, should be conducted to identify similar injection points. Organizations should also monitor logs for suspicious query patterns or repeated failed requests targeting the vulnerable parameter. Restricting database user permissions to the minimum necessary can limit the impact of a successful injection. Finally, consider upgrading to newer, supported versions of the software that address this and other vulnerabilities.

Description

CVE-2023-53877 is a critical SQL injection vulnerability in Phpjabbers Bus Reservation System version 1.1. It arises from improper neutralization of special elements in the 'pickup_id' parameter, allowing attackers to manipulate backend SQL queries. Exploitation techniques include boolean-based, error-based, and time-based blind SQL injection, enabling attackers to extract sensitive database information without authentication or user interaction. The vulnerability has a CVSS 4.0 score of 9.3, indicating high impact on confidentiality and integrity with no required privileges. European organizations using this system risk data breaches, potentially exposing customer and operational data. Mitigation requires immediate patching or applying input validation and parameterized queries. Countries with significant transport and tourism sectors using this software are at higher risk.

Impact

For European organizations using the Phpjabbers Bus Reservation System 1.1, this vulnerability poses a significant risk of data breaches involving customer personal information, travel itineraries, and payment details. Attackers could exfiltrate sensitive data, leading to privacy violations and regulatory non-compliance under GDPR. Manipulation of database queries could also disrupt reservation operations, causing service outages or incorrect bookings, impacting business continuity and customer trust. The critical severity and ease of exploitation mean attackers can launch automated attacks at scale, potentially targeting multiple organizations simultaneously. This could also facilitate further attacks such as privilege escalation or lateral movement if the compromised database contains credentials or internal network information. The reputational damage and potential fines for data protection violations could be substantial. Transport and tourism sectors, which rely heavily on reservation systems, would be particularly vulnerable to operational and financial impacts.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 22 Dec 2025, 21:51 UTC

Technical details

References

Community reviews

Related threats