CVE-2025-6578
BaseFortify
Publication date: 2025-06-24
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-6578 is a critical SQL injection vulnerability in the Simple Online Hotel Reservation System version 1.0, specifically in the /admin/delete_account.php file. The vulnerability occurs because the 'admin_id' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This flaw enables attackers to manipulate SQL queries remotely without authentication, potentially accessing, modifying, or deleting sensitive data in the database. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, allowing attackers to retrieve sensitive information, modify or delete records, and potentially gain full control over the system. It can also cause service disruptions and threaten business continuity. Since no authentication is required, the attack can be initiated remotely, making it particularly severe. [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 /admin/delete_account.php endpoint for SQL injection via the admin_id parameter. A practical method is to use sqlmap targeting the URL with the admin_id parameter to confirm injection. For example, using sqlmap with a command like: sqlmap -u "http://<target>/admin/delete_account.php?admin_id=1" --batch --level=5 --risk=3. Additionally, a time-based blind SQL injection test can be performed by injecting payloads that cause delays, such as admin_id=115'+(SELECT 0x596e7656 WHERE 3972=3972 AND (SELECT SLEEP(5)))+' to observe response delays indicating vulnerability. Also, Google dorking with queries like inurl:admin/delete_account.php can help locate vulnerable instances. [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 admin_id parameter, and minimizing database user permissions by avoiding use of high-privilege accounts for routine operations. Regular security audits of code and systems should be conducted to detect and address vulnerabilities promptly. If possible, replacing the affected software with an alternative product is recommended as no known countermeasures are identified. [2, 3]