Skip to main content
VulnerabilityPublished

CVE-2025-6767: sfturing hosp_order · SQL Injection

Affects sfturing hosp_orderSource CVE Database V5

0

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

  1. Immediate code review and sanitization: Developers should audit the findDoctorByCondition function to ensure proper parameterized queries or prepared statements are used to prevent SQL Injection.
  2. Input validation: Implement strict validation and sanitization of the hospitalName input to reject malicious payloads.
  3. Web application firewall (WAF): Deploy a WAF with SQL Injection detection rules to block suspicious requests targeting this parameter.
  4. Monitoring and logging: Enhance logging around database queries involving hospitalName to detect anomalous activity.
  5. Vendor engagement: Engage with sfturing to obtain patches or updates addressing this vulnerability.
  6. Network segmentation: Isolate the hosp_order system within the network to limit exposure.
  7. Access controls: Restrict database user privileges to the minimum necessary to reduce potential damage from injection attacks.
  8. Incident response readiness: Prepare for potential exploitation by having response plans and backups in place. These steps go beyond generic advice by focusing on immediate code-level fixes, compensating controls, and organizational preparedness tailored to this specific vulnerability.

Description

A vulnerability was found in sfturing hosp_order up to 627f426331da8086ce8fff2017d65b1ddef384f8. It has been rated as critical. This issue affects the function findDoctorByCondition of the file DoctorServiceImpl.java. The manipulation of the argument hospitalName leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available.

References

Community reviews

Loading reviews…