CVE-2023-25813

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

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

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2023-02-22. NVD baseline CVSS 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2023-0814 (ENISA EUVD) · GHSA-wrh9-cjv3-2hpw (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
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).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.4%CVSS: 10.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Sequelize is a Node.js ORM tool. In versions prior to 6.19.1 a SQL injection exploit exists related to replacements. Parameters which are passed through replacements are not properly escaped which can lead to arbitrary SQL injection depending on the specific queries in use. The issue has been fixed in Sequelize 6.19.1. Users are advised to upgrade. Users unable to upgrade should not use the replacements and the where option in the same query.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
76
EG Risk 76/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)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.4%
EPSS %ILE
73rd
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 (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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, Track* at medium and Attend at high mission impact.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, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (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

February 22, 2023

Last Modified

November 21, 2024

Advisory Details (4)

Auto-updated Nov 1, 2026
Patch available. Sources: github_release, github, github_commit.
GitHub advisoryMentions a patch (unverified)

SQL Injection via replacements · Advisory · sequelize/sequelize · GitHub

https://github.com/sequelize/sequelize/security/advisories/GHSA-wrh9-cjv3-2hpw
GitHub release Patch Available

v6.19.1

Patch available: sequelize/sequelize v6.19.1

https://github.com/sequelize/sequelize/releases/tag/v6.19.1
Web page

PSA: Upgrade to Sequelize >= 6.19.2 & Our recent breaking change in v6 · Issue #14519 · sequelize/sequelize · GitHub

https://github.com/sequelize/sequelize/issues/14519
GitHub commit Patch Available

commit ccaa3996047f (sequelize/sequelize)

Patch available: sequelize/sequelize v6.34.0 (contains commit ccaa3996047f)

https://github.com/sequelize/sequelize/commit/ccaa3996047fe00048d5993ab2dd43ebadd4f78b

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmsequelize @ 6.19.1 (fixes < 6.19.1)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
sequelize—
  • every version up to 6.19.1: fixed in 6.19.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 52× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 98 of 225 refreshes 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 127 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2023-25813?
CVE-2023-25813 is a critical-severity vulnerability; its CVE record was published on February 22, 2023. Sequelize is a Node.js ORM tool. In versions prior to 6.19.1 a SQL injection exploit exists related to replacements. Parameters which are passed through replacements are not properly escaped which can lead to arbitrary SQL injection depending on the specific queries in use. The issue has been fixed…
When was the CVE record for CVE-2023-25813 published?
The CVE record for CVE-2023-25813 was published on February 22, 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 November 21, 2024; the record at its source may have been updated since.
Is CVE-2023-25813 actively exploited?
CVE-2023-25813 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% probability of exploitation in the next 30 days (73rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-25813?
CVE-2023-25813 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2023-25813?
A fix for CVE-2023-25813 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-25813

Explore →

Is Your Infrastructure Affected by CVE-2023-25813?

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