LiveActive security incident?Get immediate response
CVE Record

CVE-2023-22578: Sequalize - Default support for “raw attributes” when using parentheses

Due to improper artibute filtering in the sequalize js library, can a attacker peform SQL injections.

CriticalCVSS 10Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This CVE describes a SQL injection risk in the Sequelize.js library as packaged in the provided Feathers-Sequalize/Sequelize.js affected entry. If an application exposes vulnerable query construction to attackers, database confidentiality, integrity, and availability could be at risk.

Executive priority

Treat as urgent for internet-facing systems using the affected library range. SQL injection can create direct business impact through data theft, data modification, or service disruption, but first confirm actual dependency use and reachable query paths.

Technical view

The source bundle attributes CVE-2023-22578 to improper attribute filtering involving default support for raw attributes when parentheses are used. The affected version range is listed as Sequelize.js before v7.0.0-alpha.20. CVSS is 10.0 with network attack, low complexity, no privileges, and no user interaction.

Likely exposure

Exposure is likely in applications that use the listed affected Sequelize.js version range and allow attacker-influenced query attributes. The bundle does not identify specific applications, deployments, or default vulnerable configurations beyond the library/version data.

Exploitation context

The source bundle does not cite active exploitation, and KEV is false. The CVSS vector indicates exploitation could be remote and unauthenticated if a vulnerable application exposes reachable query paths, but the bundle does not provide exploit prevalence or observed attacks.

Researcher notes

Evidence is limited to CVE metadata and DIVD references in the bundle. Do not assume exploitation or broader product impact. The key research task is confirming vulnerable dependency versions and whether attacker-controlled input can influence Sequelize attribute selection.

Mitigation direction

  • Inventory applications using the listed Sequelize.js affected version range.
  • Check DIVD and vendor guidance before selecting a fixed version.
  • Prioritize updating affected dependencies where vendor guidance confirms a safe release.
  • Review query builders that accept user-influenced attributes or raw attribute patterns.
  • Add defensive validation around externally supplied query fields pending vendor remediation.

Validation and detection

  • Review package manifests and lockfiles for Sequelize.js versions below v7.0.0-alpha.20.
  • Map public routes or APIs that build Sequelize queries from request input.
  • Inspect code paths using attributes, raw attributes, or parenthesized attribute expressions.
  • Confirm database permissions limit impact from application-layer SQL injection.
  • Track whether vendor or DIVD advisories add remediation details.
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-790: 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-22578 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
10 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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
10CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H3.96Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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-790 · source CWE mapping

Improper Filtering of Special Elements

Improper Filtering of Special Elements represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.