@vendure/core has a SQL Injection vulnerability

CVE-2026-40887

Assigned byThe organization (CNA) that assigned this CVE ID and published the record, usually the vendor.
GitHub, Inc. (opens in new tab)
Published
Last modified
NVD status
Deferred
CVSS 3.19.1Critical

Description

Vendure is an open-source headless commerce platform. Starting in version 1.7.4 and prior to versions 2.3.4, 3.5.7, and 3.6.2, an unauthenticated SQL injection vulnerability exists in the Vendure Shop API. A user-controlled query string parameter is interpolated directly into a raw SQL expression without parameterization or validation, allowing an attacker to execute arbitrary SQL against the database. This affects all supported database backends (PostgreSQL, MySQL/MariaDB, SQLite). The Admin API is also affected, though exploitation there requires authentication. Versions 2.3.4, 3.5.7, and 3.6.2 contain a patch. For those who are unable to upgrade immediately, Vendure has made a hotfix available that uses RequestContextService.getLanguageCode to validate the languageCode input at the boundary. This blocks injection payloads before they can reach any query. The hotfix replaces the existing getLanguageCode method in packages/core/src/service/helpers/request-context/request-context.service.ts. Invalid values are silently dropped and the channel's default language is used instead. The patched versions additionally convert the vulnerable SQL interpolation to a parameterized query as defense in depth.

Exploitation

Whether attackers are exploiting this vulnerability, and how likely they are to try in the next 30 days.

CISA SSVC assessmentAbout SSVC (opens in new tab)

CISA's assessment of whether it's exploited, whether attacks can be automated and how much control an attacker gains.

ExploitationWhether CISA has seen exploit code or attacks for this vulnerability.
None known
AutomatableWhether attackers can exploit it at scale without manual steps.
Yes
Technical impactHow much control of the affected system an attacker gains.
Partial control
Assessed

FIRST Exploit Prediction Scoring System (EPSS)About EPSS (opens in new tab)

FIRST's estimate of the chance attackers try to exploit this vulnerability in the next 30 days.

Probability of exploitationIt predicts attempts, not success, and is updated daily.
1.762%
Compared with other CVEs
At or above 78.511% of scored CVEs
Scored

Affected products

The products and versions with the vulnerability.

Listed by CNA

The products and versions affected, according to the organization that published this CVE.

VendorProductAffected versions
vendurehqvendure
  • >= 3.0.0, < 3.5.7
  • >= 3.6.0, < 3.6.2
  • >= 1.7.4, < 2.3.4

Severity

How serious the vulnerability is if exploited, scored from 0 to 10 with the CVSS standard (opens in new tab).

  • 9.1 CriticalCVSS 3.1 · SecondaryPrimary scores are NVD's own. Secondary scores come from the organization that published the CVE, or from CISA. · Scored by GitHub, Inc. (opens in new tab)
    Attack vectorWhere the attacker has to be. Network is the widest: anywhere on the Internet.
    Network
    Attack complexityWhether the attack depends on conditions the attacker doesn't control.
    Low
    Privileges requiredThe access the attacker needs before attacking.
    None
    User interactionWhether someone other than the attacker has to do something, like open a link.
    None
    ScopeWhether the attack can reach beyond the vulnerable component.
    Unchanged
    ConfidentialityHow much data the attacker can read.
    High
    IntegrityHow much data the attacker can change.
    None
    AvailabilityHow much the attacker can disrupt the system or service.
    High

    CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HView in FIRST's calculator (opens in new tab)

Weaknesses and attack patterns

The type of bug behind the vulnerability, and how attackers exploit that type.

  • Improper Neutralization of Special Elements used in an SQL Command · CWE-89 (opens in new tab)

    The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

    Likelihood of exploitHow likely MITRE rates attacks on this type of weakness, in general rather than for this vulnerability.
    High
    Abstraction
    Base
    Mapping guidance
    Allowed
    Part of

References

Advisories, patches, exploits and more about this vulnerability.

This product uses the NVD API but is not endorsed or certified by the NVD (opens in new tab). CVE records from the CVE List (opens in new tab), weakness types from MITRE's CWE (opens in new tab)™ and attack patterns from its CAPEC (opens in new tab)™ are © The MITRE Corporation, used under the CVE (opens in new tab), CWE (opens in new tab) and CAPEC (opens in new tab) terms of use. Known exploited vulnerabilities and SSVC assessments are from CISA. Exploit predictions are from FIRST's EPSS (opens in new tab). About this data