CVE 9.1 CRITICAL

@vendure/core has a SQL Injection vulnerability_CVE-2026-40887

9.1 / 10
CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

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.

AI Analysis

Unauthenticated SQL injection vulnerability in Vendure Shop API

Basic Information

ID CVE-2026-40887
Source GitHub_M
Published Apr 21, 2026 at 19:24

Affected Product

Vendor vendurehq
Product vendure
Version >= 3.0.0, < 3.5.7
Affected Versions vendurehq vendure >= 3.0.0, < 3.5.7
vendurehq vendure >= 3.6.0, < 3.6.2
vendurehq vendure >= 1.7.4, < 2.3.4

CWE Classification

AI Assessment

AI Score 9.1 / 10
AI Severity Critical
Vendor Vendure
Product Vendure Core
Version 1.7.4-2.3.4, 3.0.0-3.5.7, 3.6.0-3.6.2

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.