Skip to content
Fencer Intel
critical 9.9

CVE-2023-22579 json

Sequalize - Unsafe fall-through in getWhereConditions

published 3y ago modified 4mo ago also EUVD-2023-0801 , GHSA-vqfx-gj96-3w95

cvss
9.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 57%
public exploits
0
none known

Summary

Due to improper parameter filtering in the sequalize js library, can a attacker peform injection.

Patch / fix

  • npm sequelize 6.28.1
  • npm @sequelize/core 7.0.0-alpha.20
  • sequelizejs sequelize 6.28.1

Is CVE-2023-22579 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

0.81% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-15).

CVSS scores

assigned by version score vector
CNA 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
GitHub 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
npm sequelize
<6.28.1
6.28.1
npm @sequelize/core
<7.0.0-alpha.20
7.0.0-alpha.20

Affected products

  • Feathers-Sequalize Sequelize.js

Classification

Weakness
  • CWE-843 Access of Resource Using Incompatible Type

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of sequelize/sequelize published their own advisory on GitHub. Reviewed sources take precedence over it.