CVE-2025-15450
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability was identified in sfturing hosp_order up to 627f426331da8086ce8fff2017d65b1ddef384f8. Affected by this vulnerability is the function findOrderHosNum of the file /ssm_pro/orderHos/. Such manipulation of the argument hospitalAddress/hospitalName leads to sql injection. The attack can be launched remotely. The exploit is publicly available and might be used. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The vendor was contacted early about this disclosure but did not respond in any way.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSQL injection vulnerability in the findOrderHosNum function of the sfturing hosp_order application. The hospitalAddress and hospitalName parameters are not properly sanitized before being used in SQL queries, allowing an attacker to inject malicious SQL code remotely.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the sfturing hosp_order applicationSearch for files or modules named 'hosp_order', 'orderHos', or 'sfturing' in your application directory. Check your deployed web application's source code for references to 'sfturing' and 'hosp_order' modules.Affected if The sfturing hosp_order application or module is present in your environment
-
Determine the hosp_order component versionInspect the application's version manifest, build files (pom.xml, package.json, requirements.txt), or assembly descriptors where the hosp_order or sfturing component version is defined. Compare against any available version information from your vendor.Affected if The installed version of hosp_order falls within the affected range (if known) or is an unpatched version containing the findOrderHosNum function
-
Identify the findOrderHosNum functionSearch the hosp_order source code for the 'findOrderHosNum' function definition. Verify that it accepts hospitalAddress and hospitalName as input parameters.Affected if The findOrderHosNum function exists and processes hospitalAddress and hospitalName parameters
-
Examine SQL query construction in findOrderHosNumReview the findOrderHosNum function source code to identify how hospitalAddress and hospitalName are incorporated into SQL queries. Look for string concatenation, direct string interpolation, or non-parameterized query builders.Affected if The parameters are directly concatenated into SQL queries without using parameterized queries, prepared statements, or input sanitization
-
Verify exposure of the vulnerable endpointCheck if the findOrderHosNum function is exposed via an API endpoint, web service, or other remote interface that accepts user-supplied hospitalAddress and hospitalName values.Affected if The function is accessible remotely and accepts unsanitized user input for these parameters
Your environment is affected if the sfturing hosp_order application with the vulnerable findOrderHosNum function is deployed and the hospitalAddress/hospitalName parameters are used in unsanitized SQL queries accessible to remote users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedReplace dynamic SQL queries with parameterized queries/prepared statements for the hospitalAddress and hospitalName inputs. Perform input validation and audit all other functions in the orderHos module for similar injection vulnerabilities.
- 1. Locate the findOrderHosNum function in the file /ssm_pro/orderHos/
- 2. Audit the function for direct use of hospitalAddress or hospitalName arguments in SQL queries
- 3. Replace any string concatenation or direct interpolation of these parameters with parameterized queries (prepared statements)
- 4. Implement input validation: sanitize hospitalAddress and hospitalName by validating against expected patterns (e.g., alphanumeric, allowed characters only) before database interaction
- 5. Apply principle of least privilege: ensure the database user used by the application has minimal required permissions
- 6. If possible, add Web Application Firewall (WAF) rules to detect and block SQL injection patterns in these parameters
- 7. Test the remediation by attempting common SQL injection payloads in hospitalAddress and hospitalName fields
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-15450 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-15450 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data