CVE-2025-6457
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 | 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-6457 is a critical SQL injection vulnerability in the Online Hotel Reservation System 1.0, specifically in the /reservation/demo.php file. It occurs because the 'start' parameter, received via POST requests, is not properly validated or sanitized. This allows attackers to inject malicious SQL code, manipulating database queries remotely without needing authentication. [1]
How can this vulnerability impact me? :
This vulnerability can allow attackers to gain unauthorized access to the database, leak sensitive information, modify or delete data, take control of the system, and cause service interruptions. These impacts can severely compromise system security and disrupt business operations. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the vulnerable parameter `start` in POST requests to the URL `/reservation/demo.php` for SQL injection. You can use tools like sqlmap to automate detection. For example, run: sqlmap -u "http://127.0.0.1/newhotel/reservation/demo.php" --data="start=2025-06-13&end=2025-06-17&result=4" -p start --batch. Additionally, manual testing can be done by injecting payloads such as `start=13/06/2025' OR NOT 6506=6506 #` or `start=13/06/2025' OR SLEEP(5) #` in POST data and observing the response for anomalies or delays indicating SQL injection. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding for the `start` parameter to prevent SQL injection. 2) Apply strict input validation and filtering to ensure the `start` parameter conforms to expected date formats. 3) Restrict database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. 4) Conduct a security audit of the code and system to identify and remediate vulnerabilities promptly. [1]