CVE-2023-45055

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2023-11-06. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2023-49376 (ENISA EUVD) · GHSA-772v-9mr6-2jg6 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

Update to 4.0.7 or a higher version (from the CVE record's solution, Patchstack) — apply it.

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in InspireUI MStore API allows SQL Injection.This issue affects MStore API: from n/a through 4.0.6.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: Update to 4.0.7 or a higher version (from the CVE record's solution, Patchstack). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
53rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-13). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

Update to 4.0.7 or a higher version (from the CVE record's solution, Patchstack). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 6, 2023

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Nov 2, 2026
Fix named in the CVE record's solution (Patchstack).

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 60× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 322 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 222 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 17:42 UTCEchelonGraph re-scored
  2. 2026-11-13 17:41 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-11-13 16:45 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  4. 2026-11-12 18:15 UTCEchelonGraph re-scored
  5. 2026-11-12 18:15 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-11-12 16:30 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  7. 2026-11-11 19:27 UTCEchelonGraph re-scored
  8. 2026-11-11 19:27 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-11-11 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  10. 2026-11-10 20:39 UTCEchelonGraph re-scored
  11. 2026-11-10 20:39 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-11-10 16:37 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  13. 2026-11-09 21:41 UTCEchelonGraph re-scored
  14. 2026-11-09 21:41 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-11-09 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  16. 2026-11-08 22:54 UTCEchelonGraph re-scored
  17. 2026-11-08 22:54 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-11-08 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  19. 2026-11-08 00:07 UTCEchelonGraph re-scored
  20. 2026-11-08 00:07 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-11-07 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  22. 2026-11-07 01:19 UTCEchelonGraph re-scored
  23. 2026-11-07 01:19 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-11-06 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  25. 2026-11-06 02:30 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-11-06 02:30 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-11-05 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  3. 2026-11-05 03:43 UTCEchelonGraph re-scored
  4. 2026-11-05 03:43 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-11-04 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  6. 2026-11-04 04:56 UTCEchelonGraph re-scored
  7. 2026-11-04 04:56 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-11-03 16:41 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  9. 2026-11-03 06:08 UTCEchelonGraph re-scored
  10. 2026-11-03 06:08 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-11-02 16:40 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  12. 2026-11-02 07:19 UTCEchelonGraph re-scored
  13. 2026-11-02 07:19 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  15. 2026-11-01 08:31 UTCEchelonGraph re-scored
  16. 2026-11-01 08:31 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  18. 2026-10-31 09:43 UTCEchelonGraph re-scored
  19. 2026-10-31 09:43 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  21. 2026-10-30 10:56 UTCEchelonGraph re-scored
  22. 2026-10-30 10:56 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  24. 2026-10-29 12:10 UTCEchelonGraph re-scored
  25. 2026-10-29 12:09 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  27. 2026-10-28 13:15 UTCEchelonGraph re-scored
  28. 2026-10-28 13:14 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  29. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  30. 2026-10-27 14:23 UTCEchelonGraph re-scored
  31. 2026-10-27 14:23 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-10-26 16:28 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  33. 2026-10-26 15:25 UTCEchelonGraph re-scored
  34. 2026-10-26 15:24 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  35. 2026-10-25 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  36. 2026-10-25 15:55 UTCEchelonGraph re-scored
  37. 2026-10-25 15:55 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  38. 2026-10-24 17:06 UTCEchelonGraph re-scored
  39. 2026-10-24 17:06 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  40. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  41. 2026-10-23 18:19 UTCEchelonGraph re-scored
  42. 2026-10-23 18:19 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  44. 2026-10-22 19:31 UTCEchelonGraph re-scored
  45. 2026-10-22 19:31 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  47. 2026-10-21 20:44 UTCEchelonGraph re-scored
  48. 2026-10-21 20:44 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  50. 2026-10-20 21:55 UTCEchelonGraph re-scored
  51. 2026-10-20 21:55 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  53. 2026-10-19 23:07 UTCEchelonGraph re-scored
  54. 2026-10-19 23:07 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  55. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  56. 2026-10-18 22:33 UTCEchelonGraph re-scored
  57. 2026-10-18 22:33 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-10-18 07:49 UTCEchelonGraph re-scored
  59. 2026-10-17 23:28 UTCEchelonGraph re-scored
  60. 2026-10-17 23:27 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  62. 2026-10-17 00:38 UTCEchelonGraph re-scored
  63. 2026-10-17 00:38 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  65. 2026-10-16 00:31 UTCEchelonGraph re-scored
  66. 2026-10-16 00:31 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  68. 2026-10-14 19:05 UTCEchelonGraph re-scored
  69. 2026-10-14 19:05 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  71. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  72. 2026-10-13 15:32 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  73. 2026-10-12 16:40 UTCEchelonGraph re-scored
  74. 2026-10-12 16:39 UTCGHSA enrichmentGHSA-772v-9mr6-2jg6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  75. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile

Frequently asked(5)

What is CVE-2023-45055?
CVE-2023-45055 is a critical-severity vulnerability; its CVE record was published on November 6, 2023. Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in InspireUI MStore API allows SQL Injection.This issue affects MStore API: from n/a through 4.0.6.
When was the CVE record for CVE-2023-45055 published?
The CVE record for CVE-2023-45055 was published on November 6, 2023. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2023-45055 actively exploited?
CVE-2023-45055 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-45055?
CVE-2023-45055 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2023-45055?
The CVE record's solution for CVE-2023-45055, written by its CNA Patchstack, names the fix: "Update to 4.0.7 or a higher version."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-45055

Explore →

Is Your Infrastructure Affected by CVE-2023-45055?

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