Skip to main content

PostgreSQL CVE-2026-40887

CRITICAL
SQL Injection (CWE-89)
2026-04-14 https://github.com/vendurehq/vendure GHSA-9pp3-53p2-ww9v
9.1
CVSS 3.1 · GitHub Advisory
Share

Severity by source

GitHub Advisory PRIMARY
9.1 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

Lifecycle Timeline

3
PoC Detected
Apr 22, 2026 - 21:08 vuln.today
Public exploit code
Patch released
Apr 16, 2026 - 02:30 nvd
Patch available
CVE Published
Apr 14, 2026 - 22:38 nvd
CRITICAL 9.1

Blast Radius

ecosystem impact
† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth
  • 1 npm packages depend on @vendure/core (1 direct, 0 indirect)

Ecosystem-wide dependent count for version 3.0.0.

DescriptionGitHub Advisory

Summary

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.

Affected versions

  • @vendure/core < 2.3.4
  • @vendure/core >= 3.0.0, < 3.5.7
  • @vendure/core >= 3.6.0, < 3.6.2

Note: versions 2.3.4 and above in the 2.x line are patched. There were no 2.4.x or 2.x releases between 2.3.x and 3.0.0.

Patched versions

  • @vendure/core 2.3.4
  • @vendure/core 3.5.7
  • @vendure/core 3.6.2

Details

In ProductService.findOneBySlug, the request context's languageCode value is interpolated into a SQL CASE expression via a JavaScript template literal:

ts
.addSelect(
    `CASE translation.languageCode WHEN '${ctx.languageCode}' THEN 2 WHEN '${ctx.channel.defaultLanguageCode}' THEN 1 ELSE 0 END`,
    'sort_order',
)

TypeORM has no opportunity to parameterize this value because it is embedded directly into the SQL string before being passed to the query builder.

The languageCode value can originate from the HTTP query string and is set on the request context for every incoming API request. The value is cast to the LanguageCode TypeScript type at compile time, but no runtime validation is performed -- the raw query string value is used as-is.

Attack vector

An unauthenticated attacker can append a crafted languageCode query parameter to any Shop API request to inject arbitrary SQL into the query. No user interaction is required. The vulnerable endpoint is exposed on every default Vendure installation.

Mitigation

Upgrade to a patched version immediately.

If you cannot upgrade right away, apply the following hotfix to RequestContextService.getLanguageCode to validate the languageCode input at the boundary. This blocks injection payloads before they can reach any query:

ts
private getLanguageCode(req: Request, channel: Channel): LanguageCode | undefined {
    const queryLanguageCode = req.query?.languageCode as string | undefined;
    const isValidFormat = queryLanguageCode && /^[a-zA-Z0-9_-]+$/.test(queryLanguageCode);
    return (
        (isValidFormat ? (queryLanguageCode as LanguageCode) : undefined) ??
        channel.defaultLanguageCode ??
        this.configService.defaultLanguageCode
    );
}

This 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.

Analysis

{ctx.languageCode}' THEN 2 WHEN '${ctx.channel.defaultLanguageCode}' THEN 1 ELSE 0 END, 'sort_order', ) TypeORM has no opportunity to parameterize this value because it is embedded directly into the SQL string before being passed to the query builder. The languageCode value can originate from the HTTP query string and is set on the request context for every incoming API request. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

CVE-2026-40887 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy