CVE-2025-15450
SQL Injection in sfturing hosp_order's findOrderHosNum Function
Publication date: 2026-01-05
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 |
|---|---|---|
| sfturing | hosp_order | to 627f426331da8086ce8fff2017d65b1ddef384f8 (exc) |
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-15450 is an SQL injection vulnerability in the open-source hospital appointment registration system 'hosp_order.' It occurs in the function findOrderHosNum, where user inputs hospitalAddress and hospitalName are directly concatenated into SQL queries without proper sanitization or parameterization. This allows attackers to manipulate the SQL query by injecting malicious code through these input fields, potentially leading to unauthorized data access or modification. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can allow remote attackers to perform SQL injection attacks, which may lead to unauthorized access, modification, or deletion of sensitive data within the hospital appointment system's database. It compromises the confidentiality, integrity, and availability of the affected system, potentially exposing sensitive patient or hospital information and disrupting normal operations. [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 monitoring for unusual or malicious SQL injection attempts targeting the parameters hospitalAddress and hospitalName in requests to the /ssm_pro/orderHos/ endpoint. A proof-of-concept exploit involves sending a POST request with manipulated hospitalName or hospitalAddress parameters. You can detect attempts by inspecting web server logs or using tools like curl to test injection points. For example, a command to test might be: curl -X POST https://<target>/ssm_pro/orderHos/1 -d "hospitalName=' OR '1'='1" -v Additionally, using web application firewalls (WAF) or intrusion detection systems (IDS) with SQL injection detection rules can help identify exploitation attempts. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting or disabling access to the vulnerable endpoint /ssm_pro/orderHos/, applying input validation and sanitization on hospitalAddress and hospitalName parameters, and implementing parameterized queries or prepared statements to prevent SQL injection. Since no patches or vendor responses are available, consider replacing the affected software with an alternative product. Additionally, monitor logs for suspicious activity and deploy web application firewalls (WAF) to block SQL injection attempts. [3, 2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not explicitly discuss the impact of this SQL injection vulnerability on compliance with common standards and regulations such as GDPR or HIPAA. However, since the vulnerability allows unauthorized access and potential modification of sensitive hospital appointment data, it could lead to violations of data protection and privacy regulations by exposing or compromising personal health information. Therefore, organizations using the affected software might face compliance risks related to confidentiality and integrity of protected data. [1, 2, 3]