LiveActive security incident?Get immediate response
CVE Record

CVE-2023-22579: Sequalize - Unsafe fall-through in getWhereConditions

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

CriticalCVSS 9.9Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This CVE describes an injection risk in the Sequelize JavaScript library path named getWhereConditions. A logged-in attacker with low privileges may influence filtered parameters and affect confidentiality, integrity, and availability. The source bundle rates it critical, but provides limited implementation detail.

Executive priority

Treat as high-priority for internet-facing or multi-user applications using the affected dependency. The impact rating is critical, but remediation should be source-validated because the public bundle is brief and product naming is inconsistent.

Technical view

CVE-2023-22579 is reported as improper parameter filtering causing unsafe fall-through in getWhereConditions. The CVSS 3.1 vector is 9.9: network reachable, low complexity, low privileges required, no user interaction, changed scope, and high CIA impact. CWE-843 is listed.

Likely exposure

Exposure is most likely in applications using the affected Feathers-Sequalize or Sequelize.js dependency versions below v7.0.0-alpha.20, especially where user-controlled values reach query-building logic.

Exploitation context

The source bundle does not identify CISA KEV listing or active exploitation. It does indicate a critical, network-reachable issue requiring only low privileges, so authenticated application users may represent a realistic threat model.

Researcher notes

Evidence is limited to CVE metadata and DIVD references. Confirm package identity, vulnerable call paths, and fixed release details before asserting exploitability in a specific application.

Mitigation direction

  • Inventory applications using Feathers-Sequalize or Sequelize.js.
  • Identify versions below v7.0.0-alpha.20.
  • Review vendor and DIVD guidance for confirmed fixed versions.
  • Upgrade affected dependencies where vendor guidance supports it.
  • Add defensive validation around user-controlled query filters.

Validation and detection

  • Check dependency manifests and lockfiles for affected package versions.
  • Trace whether user input reaches getWhereConditions or query filters.
  • Review authentication boundaries for low-privilege users.
  • Run regression tests for query filtering behavior.
  • Monitor vendor advisories for clarifications or corrected metadata.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-843: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-22579 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.9CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.9Critical
CVSS 3.1 vector shape for CVE-2023-22579Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Feathers-SequalizeSequelize.js<v7.0.0-alpha.20unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-843 · source CWE mapping

Access of Resource Using Incompatible Type ('Type Confusion')

Access of Resource Using Incompatible Type ('Type Confusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.