CVE-2025-10843
BaseFortify
Publication date: 2025-09-23
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 |
|---|---|---|
| fabianros | 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-10843 is a critical SQL injection vulnerability in the Online Hotel Reservation System 1.0, specifically in the file /reservation/paypalpayout.php. The vulnerability occurs because the 'confirm' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This can lead to unauthorized access to the database, data leakage, modification, or deletion, and potentially full system compromise. The attack can be performed remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to remotely execute arbitrary SQL commands on your database without authentication. This can result in unauthorized access to sensitive data, data manipulation or deletion, exposure of confidential information, and disruption of service. It threatens the confidentiality, integrity, and availability of your system and data, potentially leading to full system compromise. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
The vulnerability can be detected by testing the 'confirm' parameter in the /reservation/paypalpayout.php file for SQL injection using various SQL injection techniques such as boolean-based blind, time-based blind, and UNION query injections. Example payloads include: - Boolean-based blind: confirm=-1732' OR 1547=1547# - Time-based blind: confirm=' AND (SELECT 8714 FROM (SELECT(SLEEP(5)))rsnN)-- - UNION query: confirm=' UNION ALL SELECT NULL,NULL,CONCAT(0x71626a7a71,0x484e6c75414c74705a416c565a4552446a6d6d73525241797668537056654a736376636d70707a56,0x7162707871),NULL,NULL,NULL,NULL# Additionally, the sqlmap tool can be used to automate detection and exploitation of this SQL injection vulnerability. Vulnerable targets can also be identified using Google dorking with the query: inurl:reservation/paypalpayout.php [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: - Use prepared statements with parameter binding to separate SQL code from user input. - Implement strict input validation and filtering to ensure inputs conform to expected formats. - Minimize database user permissions, avoiding use of high-privilege accounts like root or admin for routine operations. - Conduct regular security audits to detect and remediate vulnerabilities promptly. If possible, replace the affected software with an alternative product as no known mitigations or countermeasures have been documented for this specific vulnerability. [1, 2, 3]