CVE-2019-25530
SQL Injection in uHotelBooking index.php Allows Data Extraction
Publication date: 2026-03-12
Last updated on: 2026-03-12
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| hotel_booking_script | uhotelbooking_system | * |
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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': "The uHotelBooking System contains a SQL injection vulnerability in the 'system_page' GET parameter. This flaw allows unauthenticated attackers to inject malicious SQL code into database queries by sending specially crafted requests to the index.php page."}, {'type': 'paragraph', 'content': 'Attackers exploit this vulnerability using time-based blind SQL injection techniques, which involve sending payloads that cause delays based on database conditions, enabling them to extract sensitive information from the backend database without authentication.'}] [1, 2]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized execution of SQL commands on the backend database, potentially resulting in data leakage or manipulation.
Because the attack requires no authentication and has low complexity, attackers can remotely exploit it to extract sensitive information, which could compromise the confidentiality of your data.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability can be detected by sending crafted HTTP requests to the vulnerable index.php page with malicious payloads in the system_page GET parameter that use time-based blind SQL injection techniques.'}, {'type': 'paragraph', 'content': 'An example command to test for this vulnerability is to use curl or a similar HTTP client to send a request like:'}, {'type': 'paragraph', 'content': "http://localhost/[PATH]/index.php?page=3&system_page=0'XOR(if(now()=sysdate(),sleep(5),0))XOR'Z"}, {'type': 'paragraph', 'content': 'If the response is delayed by the sleep time (e.g., 5 seconds), it indicates the presence of the SQL injection vulnerability.'}] [1, 2]
What immediate steps should I take to mitigate this vulnerability?
I don't know