CVE-2025-14207
BaseFortify
Publication date: 2025-12-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 |
|---|---|---|
| tushar-2223 | hotel-management-system | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a SQL injection in the tushar-2223 Hotel-Management-System, specifically in an unknown function within the /admin/invoiceprint.php file. By manipulating the 'ID' argument, an attacker can inject malicious SQL code. The attack can be initiated remotely, and an exploit is publicly available.
How can this vulnerability impact me? :
The vulnerability allows remote attackers to perform SQL injection, which can lead to unauthorized access, data leakage, data modification, or disruption of the database. This can compromise the integrity, confidentiality, and availability of the system's data.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows unauthenticated attackers to extract sensitive data including customer details, booking records, payment information, and admin credentials. Such unauthorized access and potential data breaches can lead to non-compliance with data protection regulations like GDPR and HIPAA, which mandate the protection of personal and sensitive information. The compromise of confidentiality, integrity, and availability of data due to this SQL injection flaw poses significant risks to compliance with these standards. [1, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending crafted HTTP GET requests to the vulnerable endpoint `/admin/invoiceprint.php` with SQL injection payloads in the `id` parameter. For example, a time-based blind SQL injection test can be performed by injecting a payload that causes a delay, such as `id=1' AND (SELECT SLEEP(5)) AND '1'='1`. If the response is delayed by 5 seconds, the system is vulnerable. Additionally, automated tools like SQLMap can be used to detect and exploit this vulnerability by enumerating databases and dumping credentials without authentication. Attackers can also identify vulnerable targets using Google dorking with queries like `inurl:admin/invoiceprint.php` to find exposed endpoints. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement authentication and session validation by adding `session_start()` and verifying user sessions before processing requests, redirecting unauthenticated users to login pages. 2) Replace vulnerable SQL queries with prepared statements using parameterized queries to safely bind the `id` parameter as an integer, preventing SQL injection. 3) Centralize authentication checks in middleware included on all admin pages. 4) Validate and sanitize all input parameters to ensure they are numeric and within expected ranges. 5) Enforce least privilege on database users to limit potential damage. 6) Monitor and log suspicious activities. If possible, consider replacing the affected component with an alternative product, as no official patch is available. [3]