CVE-2025-11319
BaseFortify
Publication date: 2025-10-06
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 |
|---|---|---|
| nahiduddinahammed | hospital_management_system_website | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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?
CVE-2025-11319 is a SQL injection vulnerability in the Hospital Management System Website, specifically in the /delete.php file. The vulnerability occurs because the 'ai' parameter is directly used in an SQL DELETE statement without proper sanitization or parameterization. This allows an attacker to inject malicious SQL code, such as ' OR '1'='1', which manipulates the query to delete all records in the dashboard table instead of just one. The attack can be performed remotely and the exploit is publicly available. [1, 2]
How can this vulnerability impact me? :
This vulnerability can lead to a complete loss of user data in the affected system by allowing an attacker to delete all records in the dashboard table remotely. It compromises the confidentiality, integrity, and availability of the system, potentially disrupting hospital management operations and causing significant data loss. [1, 2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability compromises the confidentiality, integrity, and availability of sensitive data, which can lead to non-compliance with data protection regulations such as GDPR and HIPAA. Unauthorized deletion or manipulation of patient data violates requirements for data security and protection of personal health information, potentially resulting in legal and regulatory consequences. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /delete.php endpoint for SQL injection via the 'ai' parameter. One can attempt to inject SQL payloads such as ' OR '1'='1 to see if the query is vulnerable. Additionally, network detection can involve searching for HTTP requests targeting 'delete.php' with suspicious parameters. A simple curl command to test might be: curl -G 'http://target/delete.php' --data-urlencode "ai=' OR '1'='1" and observe if all records are deleted or if the response indicates SQL injection. Also, Google dorking with "inurl:delete.php" can help identify vulnerable targets. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected product with an alternative solution, as no patches or vendor responses are available. Avoid using the vulnerable /delete.php endpoint or restrict access to it. Implement input validation and parameterized queries to prevent SQL injection if you have access to the source code. Monitoring and backing up data regularly can help recover from potential data loss due to exploitation. [2]