CVE-2025-6394
BaseFortify
Publication date: 2025-06-21
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-6394 is a critical SQL injection vulnerability in version 1.0 of the Simple Online Hotel Reservation System, specifically in the /add_reserve.php file. The vulnerability occurs because the 'firstname' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This can lead to unauthorized access to the database, data leakage, modification, or deletion. The attack can be performed remotely without authentication, making it highly accessible. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, data manipulation or deletion, and potential full system compromise or service disruption. Attackers can exploit the flaw remotely without authentication, which increases the risk. The vulnerability threatens the confidentiality, integrity, and availability of the system, potentially leading to business continuity issues and loss of trust. [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 /add_reserve.php endpoint for SQL injection in the 'firstname' parameter. Tools like sqlmap can be used to automate detection. Example command: sqlmap -u "http://targetsite/add_reserve.php" --data="firstname=anyvalue" --method=POST --risk=3 --level=5. Additionally, Google dorking with the query "inurl:add_reserve.php" can help identify vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected software with a secure alternative if possible. If not, apply strict input validation and filtering on the 'firstname' parameter, use prepared statements with parameter binding to prevent SQL injection, and minimize database user permissions to reduce impact. Conduct regular security audits to detect and fix vulnerabilities promptly. [2, 3]