Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-10621: SQL Injection in SourceCodester Hotel Reservation System

0
Medium
VulnerabilityCVE-2025-10621cvecve-2025-10621
Published: Wed Sep 17 2025 (09/17/2025, 22:02:07 UTC)
Source: CVE Database V5
Vendor/Project: SourceCodester
Product: Hotel Reservation System

Description

A vulnerability was determined in SourceCodester Hotel Reservation System 1.0. The affected element is an unknown function of the file editroomimage.php. This manipulation of the argument ID causes sql injection. It is possible to initiate the attack remotely. The exploit has been publicly disclosed and may be utilized.

AI-Powered Analysis

AILast updated: 09/25/2025, 00:49:15 UTC

Technical Analysis

CVE-2025-10621 is a SQL Injection vulnerability identified in version 1.0 of the SourceCodester Hotel Reservation System, specifically within the editroomimage.php file. The vulnerability arises from improper sanitization or validation of the 'ID' parameter, which is susceptible to malicious input manipulation. An attacker can exploit this flaw remotely without requiring authentication or user interaction, by injecting crafted SQL commands through the vulnerable parameter. This can lead to unauthorized access to the backend database, potentially allowing the attacker to read, modify, or delete sensitive data related to hotel reservations, room images, or user information. The vulnerability has a CVSS 4.0 base score of 6.9, categorized as medium severity, reflecting its network attack vector, low attack complexity, and no privileges or user interaction required. The impact on confidentiality, integrity, and availability is limited but present, as the vulnerability allows partial compromise of data but does not inherently lead to full system takeover or denial of service. No public exploits are currently known in the wild, but the vulnerability details have been publicly disclosed, increasing the risk of exploitation by opportunistic attackers. The lack of available patches or official fixes at the time of publication means affected organizations must rely on mitigation strategies until a vendor patch is released.

Potential Impact

For European organizations using the SourceCodester Hotel Reservation System 1.0, this vulnerability poses a tangible risk to the confidentiality and integrity of reservation data and associated customer information. Compromise could lead to unauthorized disclosure of personal data, violating GDPR requirements and potentially resulting in regulatory penalties and reputational damage. Additionally, manipulation of reservation or room image data could disrupt business operations and customer trust. Since the vulnerability can be exploited remotely without authentication, attackers from anywhere could target these systems, increasing the threat landscape. The medium severity rating indicates that while the impact is significant, it may not lead to full system compromise or widespread service disruption. However, given the hospitality sector's reliance on customer trust and data protection, even moderate breaches can have outsized consequences. Organizations may also face indirect impacts such as increased incident response costs, legal liabilities, and loss of competitive advantage.

Mitigation Recommendations

Given the absence of an official patch, European organizations should implement immediate compensating controls. These include: 1) Applying strict input validation and parameterized queries or prepared statements in the editroomimage.php script to prevent SQL injection; if source code modification is possible, developers should sanitize and validate all user inputs rigorously. 2) Deploying Web Application Firewalls (WAFs) configured to detect and block SQL injection patterns targeting the 'ID' parameter. 3) Restricting network access to the hotel reservation system to trusted IP ranges and enforcing strong network segmentation to limit exposure. 4) Monitoring logs for unusual database query patterns or repeated failed attempts indicative of injection attempts. 5) Conducting thorough security assessments and penetration testing focused on injection vectors. 6) Planning for an urgent update or migration to a patched version once available from the vendor. 7) Ensuring regular backups of reservation data to enable recovery in case of data tampering. These measures go beyond generic advice by focusing on specific code-level fixes, network controls, and monitoring tailored to this vulnerability's characteristics.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-09-17T11:48:59.088Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68cb4e05e5fa2c8b1490b35c

Added to database: 9/18/2025, 12:10:45 AM

Last enriched: 9/25/2025, 12:49:15 AM

Last updated: 11/4/2025, 3:41:26 AM

Views: 31

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats