CVE-2025-6449
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-6449 is a critical SQL injection vulnerability in the Simple Online Hotel Reservation System version 1.0, specifically in the /admin/checkout_query.php file. The vulnerability occurs because the 'transaction_id' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This can lead to unauthorized access to the database, enabling attackers to view, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can compromise the confidentiality, integrity, and availability of the affected system. Attackers can remotely execute arbitrary SQL commands to access sensitive information, modify or delete data, and potentially disrupt services or fully compromise the system. Since no authentication is required, the attack surface is broad and the impact severe. [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/checkout_query.php file for SQL injection. You can use SQL injection testing tools such as sqlmap to automate detection and database enumeration. Example payloads for manual testing include boolean-based blind SQL injection: transaction_id=1' RLIKE (SELECT (CASE WHEN (7200=7200) THEN 1 ELSE 0x28 END))-- and time-based blind SQL injection: transaction_id=1' AND 8276=BENCHMARK(5000000,MD5(0x41446d43))--. Additionally, attackers may identify vulnerable targets using Google dorking with queries like inurl:admin/checkout_query.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, as no known countermeasures are documented. 2) If continuing to use the software, apply secure coding practices such as using prepared statements with parameter binding to prevent SQL injection. 3) Implement strict input validation and filtering on the 'transaction_id' parameter. 4) Minimize database user permissions by avoiding high-privilege accounts for routine operations. 5) Conduct regular security audits to detect and address vulnerabilities promptly. [1, 2, 3]