CVE-2025-6455
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-6455 is a critical SQL injection vulnerability in version 1.0 of the Online Hotel Reservation System by code-projects. It exists in the /messageexec.php file due to improper validation of the 'name' parameter, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, potentially leading to data modification, deletion, or exposure of sensitive information. The vulnerability can be exploited remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, leakage of sensitive information, tampering with or deletion of data, full system control by attackers, and potential service interruptions. Because it can be exploited remotely and easily, it poses a severe risk to system security and data integrity. [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 checking for the presence of the vulnerable file /messageexec.php and testing the 'name' parameter for SQL injection. One method is to use Google dorking with the query "inurl:messageexec.php" to identify potentially vulnerable targets. Additionally, manual or automated SQL injection testing tools can be used to send payloads to the 'name' parameter and observe for SQL errors or unexpected behavior. Specific commands might include using curl or sqlmap to test the parameter, for example: curl "http://target/messageexec.php?name=' OR '1'='1" or sqlmap -u "http://target/messageexec.php?name=test" --risk=3 --level=5. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements (parameterized queries) to handle user input safely, applying strict input validation and filtering on the 'name' parameter, and minimizing database user permissions by avoiding high-privilege accounts for routine operations. Regular security audits should also be conducted to detect and address vulnerabilities promptly. If possible, replacing the affected component with an alternative product is recommended. [2]