CVE-2025-11474
BaseFortify
Publication date: 2025-10-08
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 |
|---|---|---|
| nikhil-bhalerao | hotel_and_lodge_management_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-11474 is a critical SQL injection vulnerability in the SourceCodester Hotel and Lodge Management System version 1.0. It exists in the /edit_booking.php file due to improper handling and insufficient validation of the 'name' parameter. This flaw allows attackers to inject malicious SQL queries remotely without authentication, leading to unauthorized access and manipulation of the database. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, allowing attackers to extract sensitive information, modify or delete data, and disrupt service availability. This compromises the confidentiality, integrity, and availability of the system, potentially causing severe security breaches and business continuity issues. [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 /edit_booking.php endpoint for SQL injection in the 'name' parameter. A proof-of-concept involves sending a POST request manipulating the 'name' parameter, for example using sqlmap to automate detection. A sample command to test with sqlmap is: sqlmap -u "http://target/hotel2/edit_booking.php?id=15" --data="name=anything" --risk=3 --level=5. Additionally, Google dorking with queries like "inurl:edit_booking.php" can help identify potentially vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the 'name' parameter, minimizing database user privileges by avoiding high-privilege accounts for routine operations, and conducting regular security audits of code and systems. If possible, replacing or updating the affected component or product is recommended since no known countermeasures are documented. [1, 3, 2]