CVE-2025-6447
BaseFortify
Publication date: 2025-06-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 | simple_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-6447 is a critical SQL injection vulnerability in the Simple Online Hotel Reservation System version 1.0, specifically in the /admin/index.php file. The vulnerability occurs because the 'username' parameter is not properly sanitized or validated, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, allowing attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data tampering, and potential full system control. Attackers can modify or delete data, disrupt services, and compromise the confidentiality, integrity, and availability of the system. Since the exploit can be launched remotely without authentication, it poses a high risk to affected systems. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by testing the 'username' parameter in the /admin/index.php file for injection flaws. Example payloads for testing include boolean-based blind, error-based, and time-based blind SQL injection techniques. Example payloads are: - Boolean-based blind: username=test1' OR NOT 2716=2716 OR 'CdxL'='wJkb - Error-based (MySQL ≥ 5.0): username=test1' OR (SELECT 5589 FROM(SELECT COUNT(*),CONCAT(0x71787a7671,(SELECT (ELT(5589=5589,1))),0x7178767171,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a) OR 'jVvs'='MqiQ - Time-based blind (MySQL ≥ 5.0.12): username=test1' AND (SELECT 9141 FROM (SELECT(SLEEP(5)))Wlme) OR 'DHxk'='dfRM' Additionally, the sqlmap tool can be used with options such as batch mode, multiple threads, high risk and level settings, random user agents, tampering scripts (space2comment), and excluding system databases to confirm the vulnerability. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1. Use prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2. Implement strict input validation and filtering to ensure inputs conform to expected formats. 3. Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts like 'root' or 'admin' for routine operations. If possible, replace the affected software with an alternative product, as no known countermeasures or patches have been documented. [2, 3]