CVE-2025-36368

HIGHNVD 7.27.2
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.2 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 76% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
7.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.2Exploit: None knownExposed: 0

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

IBM Sterling B2B Integrator and IBM Sterling File Gateway 6.1.0.0 through 6.1.2.7_2, 6.2.0.0 through 6.2.0.5_1, and 6.2.1.0 through 6.2.1.1_1 are vulnerable to SQL injection. An administrative user could send specially crafted SQL statements, which could allow the attacker to view, add, modify, or delete information in the back-end database.

CVSS v3
7.2
EG Score
7.2(medium)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

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
Severity72% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

March 13, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Aug 2, 2026
No patch confirmed yet.
generic

Security Bulletin: IBM Sterling B2B Integrator and IBM Sterling File Gateway are Vulnerable due to SQL Injection vulnerability in Dashboard UI (CVE-2025-36368)

https://www.ibm.com/support/pages/node/7263324

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 23× 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-09-18 19:27 UTCEPSS rescore
  2. 2026-09-17 19:29 UTCEPSS rescore
  3. 2026-09-16 14:07 UTCEPSS rescore
  4. 2026-09-16 05:14 UTCEPSS rescore
  5. 2026-09-13 16:46 UTCEPSS rescore
  6. 2026-09-12 15:00 UTCEPSS rescore
  7. 2026-09-11 14:52 UTCEPSS rescore
  8. 2026-09-11 09:35 UTCEPSS rescore
  9. 2026-09-10 09:33 UTCEPSS rescore
  10. 2026-09-08 21:59 UTCEPSS rescore
  11. 2026-09-06 13:46 UTCEPSS rescore
  12. 2026-09-04 05:05 UTCEPSS rescore
  13. 2026-09-02 14:11 UTCEPSS rescore
  14. 2026-09-01 13:53 UTCEPSS rescore
  15. 2026-09-01 04:38 UTCEPSS rescore
  16. 2026-08-30 19:16 UTCEPSS rescore
  17. 2026-08-30 01:21 UTCEPSS rescore
  18. 2026-08-28 21:40 UTCEPSS rescore
  19. 2026-08-27 14:24 UTCEPSS rescore
  20. 2026-08-26 14:45 UTCEPSS rescore
  21. 2026-08-25 13:48 UTCEPSS rescore
  22. 2026-08-23 00:18 UTCEPSS rescore
  23. 2026-08-21 23:48 UTCEPSS rescore
  24. 2026-08-20 22:54 UTCEPSS rescore
  25. 2026-08-19 17:03 UTCEPSS rescore
Show 47 more
  1. 2026-08-19 17:03 UTCEPSS rescore
  2. 2026-08-18 13:47 UTCEPSS rescore
  3. 2026-08-17 13:46 UTCEPSS rescore
  4. 2026-08-16 14:55 UTCEPSS rescore
  5. 2026-08-16 11:40 UTCEG score recompute
  6. 2026-08-16 11:40 UTCGHSA enrichment
  7. 2026-08-16 02:13 UTCEPSS rescore
  8. 2026-08-15 01:29 UTCEPSS rescore
  9. 2026-08-14 20:21 UTCGHSA enrichment
  10. 2026-08-14 07:41 UTCEG score recompute
  11. 2026-08-14 07:41 UTCGHSA enrichment
  12. 2026-08-13 21:59 UTCEPSS rescore
  13. 2026-08-12 22:41 UTCEG score recompute
  14. 2026-08-12 22:41 UTCGHSA enrichment
  15. 2026-08-12 13:50 UTCEPSS rescore
  16. 2026-08-11 21:41 UTCEG score recompute
  17. 2026-08-11 21:41 UTCGHSA enrichment
  18. 2026-08-11 04:49 UTCEG score recompute
  19. 2026-08-11 04:49 UTCGHSA enrichment
  20. 2026-08-10 08:38 UTCGHSA enrichment
  21. 2026-08-09 19:59 UTCEG score recompute
  22. 2026-08-09 19:59 UTCGHSA enrichment
  23. 2026-08-09 13:46 UTCEPSS rescore
  24. 2026-08-09 07:22 UTCGHSA enrichment
  25. 2026-08-08 06:40 UTCGHSA enrichment
  26. 2026-08-07 18:02 UTCEG score recompute
  27. 2026-08-07 18:02 UTCGHSA enrichment
  28. 2026-08-07 16:26 UTCEPSS rescore
  29. 2026-08-06 19:48 UTCEG score recompute
  30. 2026-08-06 19:48 UTCGHSA enrichment
  31. 2026-08-06 13:46 UTCEPSS rescore
  32. 2026-08-06 01:55 UTCEG score recompute
  33. 2026-08-06 01:55 UTCGHSA enrichment
  34. 2026-08-04 15:09 UTCEPSS rescore
  35. 2026-08-04 10:37 UTCEPSS rescore
  36. 2026-08-04 01:11 UTCEG score recompute
  37. 2026-08-04 01:11 UTCGHSA enrichment
  38. 2026-08-03 10:35 UTCEPSS rescore
  39. 2026-08-02 17:18 UTCEG score recompute
  40. 2026-08-02 17:18 UTCGHSA enrichment
  41. 2026-08-02 02:26 UTCEPSS rescore
  42. 2026-08-01 04:15 UTCEPSS rescore
  43. 2026-07-30 16:27 UTCEPSS rescore
  44. 2026-07-30 01:29 UTCEPSS rescore
  45. 2026-07-28 15:35 UTCEPSS rescore
  46. 2026-07-27 13:39 UTCEG score recompute
  47. 2026-07-27 13:39 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2025-36368?
CVE-2025-36368 is a high vulnerability published on March 13, 2026. IBM Sterling B2B Integrator and IBM Sterling File Gateway 6.1.0.0 through 6.1.2.72, 6.2.0.0 through 6.2.0.51, and 6.2.1.0 through 6.2.1.1_1 are vulnerable to SQL injection. An administrative user could send specially crafted SQL statements, which could allow the attacker to view, add, modify, or…
When was CVE-2025-36368 disclosed?
CVE-2025-36368 was first published in the National Vulnerability Database on March 13, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-36368 actively exploited?
CVE-2025-36368 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 75.5% of all scored CVEs.
What is the CVSS score of CVE-2025-36368?
CVE-2025-36368 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2025-36368?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-36368, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-36368

Explore →

Is Your Infrastructure Affected by CVE-2025-36368?

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