CVE-2026-96548

MEDIUMPre-NVD 5.65.6—
EchelonGraph scoreHIGH confidence

Score 5.6 from GitHub Security Advisory (severity: LOW) published 2026-09-23. A secondary CVSS source baseline 5.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.6Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

A flaw has been found in sfturing hosp_order up to 627f426331da8086ce8fff2017d65b1ddef384f8. This affects an unknown part of the file ssm_pro/src/main/resources/jdbc.properties. This manipulation causes hard-coded credentials. It is possible to initiate the attack remotely. The attack's complexity is rated as high. It is indicated that the exploitability is difficult. The exploit has been published and may be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. The project was informed of the problem early through an issue report but has not responded yet.

CVSS v3
5.6
EG Score
5.6MEDIUMhigh confidence
EG Risk
30
EG Risk 30/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity56% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
16th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 23, 2026

Last Modified

September 23, 2026

Advisory Details (2)

Auto-updated Sep 23, 2026
No patch confirmed yet.
generic

GitHub - sfturing/hosp_order: 🤒医院预约挂号系统(期末项目/毕业设计) · GitHub

https://github.com/sfturing/hosp_order/
generic

Hard-coded database and SMTP credentials in repository configuration · Issue #119 · sfturing/hosp_order · GitHub

https://github.com/sfturing/hosp_order/issues/119

Vendor Advisories for CVE-2026-96548(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 20× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-03 18:47 UTCEG score recompute
  2. 2026-10-03 18:47 UTCGHSA enrichment
  3. 2026-10-03 14:26 UTCEPSS rescore
  4. 2026-10-02 18:52 UTCEG score recompute
  5. 2026-10-02 18:52 UTCGHSA enrichment
  6. 2026-10-02 17:57 UTCEPSS rescore
  7. 2026-10-01 19:51 UTCEPSS rescore
  8. 2026-10-01 19:00 UTCGHSA enrichment
  9. 2026-09-30 19:05 UTCEG score recompute
  10. 2026-09-30 19:05 UTCGHSA enrichment
  11. 2026-09-30 15:04 UTCEPSS rescore
  12. 2026-09-29 19:13 UTCEG score recompute
  13. 2026-09-29 19:13 UTCGHSA enrichment
  14. 2026-09-28 19:07 UTCEG score recompute
  15. 2026-09-28 19:06 UTCGHSA enrichment
  16. 2026-09-28 13:52 UTCEPSS rescore
  17. 2026-09-28 13:52 UTCEPSS rescore
  18. 2026-09-27 19:14 UTCEG score recompute
  19. 2026-09-27 19:14 UTCGHSA enrichment
  20. 2026-09-27 13:49 UTCEPSS rescore
  21. 2026-09-26 19:22 UTCEG score recompute
  22. 2026-09-26 19:22 UTCGHSA enrichment
  23. 2026-09-26 15:59 UTCEPSS rescore
  24. 2026-09-25 19:30 UTCGHSA enrichment
  25. 2026-09-24 19:38 UTCEG score recompute
Show 6 more
  1. 2026-09-24 19:38 UTCGHSA enrichment
  2. 2026-09-24 14:04 UTCEPSS rescore
  3. 2026-09-23 19:27 UTCEG score recompute
  4. 2026-09-23 19:26 UTCNVD updateCVSS v4 → 2.9
  5. 2026-09-23 18:39 UTCEG score recompute
  6. 2026-09-23 18:39 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-96548?
CVE-2026-96548 is a medium vulnerability published on September 23, 2026. A flaw has been found in sfturing hosporder up to 627f426331da8086ce8fff2017d65b1ddef384f8. This affects an unknown part of the file ssmpro/src/main/resources/jdbc.properties. This manipulation causes hard-coded credentials. It is possible to initiate the attack remotely. The attack's complexity is…
When was CVE-2026-96548 disclosed?
CVE-2026-96548 was first published on September 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-96548 actively exploited?
CVE-2026-96548 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-96548?
CVE-2026-96548 has a CVSS base score of 5.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-96548?
No fix for CVE-2026-96548 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-96548 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-96548

Explore →

Is Your Infrastructure Affected by CVE-2026-96548?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs