CVE-2025-6450
BaseFortify
Publication date: 2025-06-22
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| fabian | simple_online_hotel_reservation_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. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-6450 is a critical SQL injection vulnerability in the Simple Online Hotel Reservation System version 1.0, specifically in the /admin/confirm_reserve.php file. The vulnerability occurs because the 'transaction_id' parameter is not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, potentially manipulating the database by retrieving, modifying, or deleting data. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized database access, allowing attackers to view sensitive information, alter or delete data, and potentially gain full control over the system. This can result in data leakage, data tampering, service disruption, and compromise of system integrity and availability, posing a serious threat to business continuity. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'transaction_id' parameter in the /admin/confirm_reserve.php file for SQL injection. You can use tools like sqlmap to automate detection. Example sqlmap command: sqlmap -u "http://target/admin/confirm_reserve.php?transaction_id=1" --batch --dbs. Additionally, manual testing can be done using payloads such as boolean-based blind SQL injection (e.g., transaction_id=1' RLIKE (SELECT (CASE WHEN (8471=8471) THEN 1 ELSE 0x28 END))--) or time-based blind SQL injection (e.g., transaction_id=1' AND (SELECT SLEEP(5))--). Attackers can also locate vulnerable targets using Google dorking with queries like inurl:admin/confirm_reserve.php. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing the affected software with an alternative product if possible. 2) Applying prepared statements with parameter binding to prevent SQL injection. 3) Implementing strict input validation and filtering on the 'transaction_id' parameter. 4) Minimizing database user permissions by avoiding use of high-privilege accounts for routine operations. 5) Conducting regular security audits of code and systems. Since no known countermeasures or patches are documented, these steps are critical to secure the system and maintain data integrity. [1, 2, 3]