CVE-2024-10155 in Boat Booking Systeminfo

Summary

by MITRE • 10/20/2024

A vulnerability was found in PHPGurukul Boat Booking System 1.0. It has been classified as problematic. This affects an unknown part of the file book-boat.php?bid=1 of the component Book a Boat Page. The manipulation of the argument phone_number leads to cross site scripting. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Analysis

by VulDB Data Team • 03/03/2025

This vulnerability resides within the PHPGurukul Boat Booking System version 1.0, specifically targeting the book-boat.php page with bid parameter. The security flaw manifests as a cross-site scripting vulnerability that occurs when the phone_number argument is improperly handled during processing. The issue represents a classic input validation failure where user-supplied data enters the application without adequate sanitization or encoding mechanisms. This allows malicious actors to inject malicious scripts into the web application's response, which then executes in the context of other users' browsers.

The technical exploitation occurs through the manipulation of the phone_number parameter in the URL, specifically when accessing the book-boat.php?bid=1 endpoint. When an attacker crafts a malicious phone_number value containing script tags or other malicious payloads, the application fails to properly sanitize or encode this input before rendering it back to users. This vulnerability falls under CWE-79, which describes Cross-Site Scripting flaws, and more specifically aligns with CWE-74, Input Validation and Encoding, as the system fails to properly validate and encode user input before incorporating it into dynamic web content. The vulnerability's classification as remotely exploitable means that an attacker can initiate the attack without requiring physical access to the system or any privileged information.

The operational impact of this vulnerability extends beyond simple script execution, as it can lead to session hijacking, credential theft, and potentially full system compromise if attackers can leverage the XSS to target administrators or other privileged users. The public disclosure of the exploit increases the risk significantly, as it provides attackers with a ready-made method to compromise affected systems. This vulnerability directly maps to ATT&CK technique T1531, "Run-time Application Stack Modification", and T1059.007, "Command and Scripting Interpreter: JavaScript", as attackers can execute JavaScript code within user contexts. The exposure of user data through this vector could result in unauthorized access to booking information, personal contact details, and potentially financial data associated with boat reservations.

Mitigation strategies should focus on implementing robust input validation and output encoding mechanisms throughout the application. The immediate solution involves sanitizing all user inputs, particularly those that are reflected back to users, through proper HTML entity encoding and input validation routines. The application should employ Content Security Policy headers to limit script execution and prevent unauthorized code injection. Additionally, implementing proper parameter validation on the phone_number field and ensuring that all dynamic content is properly escaped before rendering will significantly reduce the attack surface. Regular security audits and code reviews should be conducted to identify similar vulnerabilities in other components, while input validation should be implemented at multiple layers including client-side and server-side validation to provide defense in depth. The system should also implement proper session management and authentication controls to limit the potential damage from any successful exploitation attempts.

Responsible

VulDB

Disclosure

10/20/2024

Moderation

accepted

CPE

ready

Exploit

Download

EPSS

0.00153

KEV

no

Activities

very low

Sources

Want to know what is going to be exploited?

We predict KEV entries!