CVE-2026-36923
SQL Injection in Sourcecodester Cab Management System Booking Module
Publication date: 2026-04-13
Last updated on: 2026-04-14
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| oretnom23 | cab_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in the Sourcecodester Cab Management System 1.0 allows attackers to execute arbitrary SQL commands and potentially extract sensitive information from the backend database.
Such unauthorized data disclosure can lead to breaches of confidentiality and data integrity, which are critical requirements under common standards and regulations like GDPR and HIPAA.
Therefore, this vulnerability could result in non-compliance with these regulations due to the risk of exposing personal or sensitive data without proper authorization or protection.
Can you explain this vulnerability to me?
The Cab Management System v1.0 by Sourcecodester has a SQL injection vulnerability in the file /cms/admin/bookings/view_booking.php. This vulnerability exists in the 'id' parameter of the URL, which is used to query the database.
An attacker can inject malicious SQL code through this 'id' parameter, such as a UNION SELECT statement, to retrieve sensitive information from the backend database, like the database name.
The attack can be performed within an authenticated session, meaning an attacker with access to a valid session could exploit this to execute arbitrary SQL commands.
How can this vulnerability impact me? :
This SQL injection vulnerability can allow an attacker to execute arbitrary SQL commands on the backend database.
- Unauthorized disclosure of sensitive data stored in the database.
- Potential modification or deletion of data, leading to data integrity issues.
- Further compromise of the system if the attacker uses the vulnerability to escalate privileges or access other parts of the system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by testing the `id` parameter in the URL `/cms/admin/bookings/view_booking.php?id=` for SQL injection payloads.
A suggested command to test this is to send an HTTP request with a payload that attempts to extract database information, such as:
- /cms/admin/bookings/view_booking.php?id=1' union select 1,2,3,4,database(),6,7,8,9,10--+
This payload uses a UNION SELECT statement to retrieve the current database name, which indicates the presence of SQL injection if successful.
Testing can be performed using tools like curl or a web browser within an authenticated session, as the vulnerability requires a valid PHP session cookie (`PHPSESSID`).
What immediate steps should I take to mitigate this vulnerability?
To mitigate the SQL injection vulnerability in Sourcecodester Cab Management System 1.0, immediate steps include:
- Avoid using the vulnerable `id` parameter in `/cms/admin/bookings/view_booking.php` until a fix is applied.
- Implement input validation and parameterized queries (prepared statements) to prevent SQL injection on the `id` parameter.
- Restrict access to the affected page to trusted users only, as the exploit requires an authenticated session.
- Monitor and review logs for suspicious activity involving the `id` parameter.
- Apply any available patches or updates from the vendor or source code maintainer addressing this vulnerability.