CVE-2025-10788
BaseFortify
Publication date: 2025-09-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?
This vulnerability is a SQL injection flaw in the Online Hotel Reservation System 1.0, specifically in the deleteroominventory.php file. It occurs because the 'id' parameter is not properly validated, allowing attackers to inject malicious SQL queries. This can lead to unauthorized access to the database. [1]
How can this vulnerability impact me? :
Exploiting this vulnerability can allow attackers to modify or delete data without authorization and expose sensitive information stored in the database. This compromises data integrity and confidentiality, potentially disrupting system operations and causing data breaches. [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 'id' parameter in the deleteroominventory.php file for SQL injection flaws. You can use tools like sqlmap to automate detection. For example, a command to test might be: sqlmap -u "http://targetsite/deleteroominventory.php?id=1" --batch --level=5 --risk=3. Additionally, manual testing by injecting SQL payloads such as ' OR '1'='1' -- into the 'id' parameter and observing the response can help detect the vulnerability. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate steps to mitigate this vulnerability include validating and sanitizing the 'id' parameter in deleteroominventory.php to prevent SQL injection. Use prepared statements or parameterized queries instead of directly including user input in SQL queries. Additionally, restrict database permissions to limit the impact of a potential exploit. Applying patches or updates from the vendor, if available, is also recommended. [1]