dbcve.org
InjectionWeakness · CWE-74

CVE-2025-6768

MEDIUM · 6.3 CVSS v3.1 Published 2025-06-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A vulnerability classified as critical has been found in sfturing hosp_order up to 627f426331da8086ce8fff2017d65b1ddef384f8. Affected is the function findAllHosByCondition of the file HospitalServiceImpl.java. The manipulation of the argument hospitalName leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available.

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 · high confidence

SQL injection vulnerability in the findAllHosByCondition function of HospitalServiceImpl.java in the sfturing hosp_order application. User-supplied input to the hospitalName parameter is directly concatenated into a SQL query without proper sanitization or parameterized queries, allowing remote attackers to inject arbitrary SQL statements.

MitigationImplement parameterized queries (PreparedStatement) for all database operations using user input, particularly in the findAllHosByCondition function. Perform comprehensive code review to identify and remediate similar SQL injection vulnerabilities across the codebase.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the sfturing hosp_order application version
    Locate the application JAR/WAR file or source code repository and check the version metadata (pom.xml, build.gradle, MANIFEST.MF, or version configuration file). Compare this version against any known affected version ranges for this CVE.
    Affected if The installed version falls within the affected version range and the vulnerable code is present.
  2. Locate the HospitalServiceImpl.java file
    Search the application source code or decompiled bytecode for the file HospitalServiceImpl.java. Verify it contains the findAllHosByCondition method.
    Affected if The file exists and contains the findAllHosByCondition function.
  3. Inspect the SQL query construction in findAllHosByCondition
    Within the findAllHosByCondition function, locate the SQL query that uses the hospitalName parameter. Check for direct string concatenation (such as 'SELECT ... WHERE hospitalName = ' + hospitalName) rather than parameterized queries using PreparedStatement with placeholders.
    Affected if The code uses direct string concatenation with the hospitalName parameter in the SQL query without parameterized queries.
  4. Verify the vulnerable endpoint is exposed
    Identify if there is a web API endpoint, controller, or service method that calls findAllHosByCondition and accepts user-supplied input for the hospitalName parameter. Check if this endpoint is accessible (internal or external network).
    Affected if The application exposes an interface that passes user input to the vulnerable findAllHosByCondition function.

A user is affected if they run a version of the sfturing hosp_order application that contains the findAllHosByCondition function with direct SQL concatenation on the hospitalName parameter, and that function is reachable via an exposed input interface.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries (PreparedStatement) for all database operations using user input, particularly in the findAllHosByCondition function. Perform comprehensive code review to identify and remediate similar SQL injection vulnerabilities across the codebase.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6768 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-6768 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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