How severe is GHSA-h9wq-xcqx-mqxm?

No CVSS score has been assigned to GHSA-h9wq-xcqx-mqxm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-h9wq-xcqx-mqxm?

GHSA-h9wq-xcqx-mqxm affects the following packages: @vendure/core (npm). Ecosystems affected: npm.

How do I fix GHSA-h9wq-xcqx-mqxm?

Update @vendure/core to 2.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h9wq-xcqx-mqxm is resolved across your whole dependency graph.

How do I detect GHSA-h9wq-xcqx-mqxm in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @vendure/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-h9wq-xcqx-mqxm if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-h9wq-xcqx-mqxm actively exploited in the wild?

No public exploit code has been indexed for GHSA-h9wq-xcqx-mqxm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-h9wq-xcqx-mqxm published, and has it been updated?

GHSA-h9wq-xcqx-mqxm was published on July 11, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Vendure Cross Site Request Forgery vulnerability impacting all API requestsGHSA-h9wq-xcqx-mqxm

Fix: vendure-ecommerce/vendure@4a10d67

GHSA-h9wq-xcqx-mqxm is a security vulnerability in @vendure/core. A fix is available for @vendure/core — see the affected versions and patch details below.

Published

Jul 11, 2023

Updated

Jul 11, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jul 11, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

59other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@vendure/corenpm

64Kdownloads / week

Description

Impact

Vendure is an e-commerce GraphQL framework with a number of APIs and different levels of authorization. By default the Cookie settings are insecure, having the SameSite setting as false which results in not having one (originates from the cookie-session npm package’s default settings).

Patches

In progress

Workarounds

Manually set the authOptions.cookieOptions.sameSite configuration option to 'strict', 'lax' or true.

References

Are there any links users can visit to find out more?

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@vendure/core`	all versions	2.0.3`npm install @vendure/core@2.0.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @vendure/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @vendure/core to 2.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h9wq-xcqx-mqxm is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact Vendure is an e-commerce GraphQL framework with a number of APIs and different levels of authorization. By default the Cookie settings are insecure, having the SameSite setting as false which results in not having one (originates from the cookie-session npm package’s default settings). ### Patches In progress ### Workarounds Manually set the `authOptions.cookieOptions.sameSite` configuration option to `'strict'`, `'lax'` or `true`. ### References _Are there any links users can visit to find out more?_

O3 Security · Impact-Aware SCA

Is GHSA-h9wq-xcqx-mqxm in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works