CVE-2025-10789
BaseFortify
Publication date: 2025-09-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 | 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
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized modification, deletion, or exposure of sensitive data stored in the database. Attackers can remotely exploit this flaw to compromise data integrity and confidentiality. [1]
Can you explain this vulnerability to me?
This vulnerability is a SQL injection flaw in the SourceCodester Online Hotel Reservation System 1.0, specifically in the deleteslide.php file. It occurs because the 'id' parameter is not properly validated, allowing attackers to inject malicious SQL commands. This can enable unauthorized access to the database. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'id' parameter in the deleteslide.php file for SQL injection flaws. You can use tools like sqlmap to automate detection, for example: sqlmap -u "http://targetsite/deleteslide.php?id=1" --batch. Alternatively, manual testing can be done by injecting SQL payloads into the 'id' parameter and observing the response for SQL errors or unexpected behavior. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate steps include applying input validation and sanitization on the 'id' parameter in deleteslide.php to prevent SQL injection. Use prepared statements or parameterized queries to handle database inputs securely. Additionally, restrict database permissions to limit the impact of potential exploitation. If a patch or update is available from the vendor, apply it promptly to remediate the vulnerability. [1]