GHSA-WM63-7627-CH33

@vendure/core's insecure currencyCode handling allows wrong payment amounts

Workarounds

You can define a custom OrderProcess onTransitionStart function which can verify the order's currencyCode is as expected before allowing the transition to the ArrangingPayment state.

Currently, in many Vendure deployments it's possible to select any currencyCode (really any, doesn't need to be assigned to the channel) and pay through Mollie and Stripe in that particular currencyCode.
The prices are not transformed. The result is the Order is in Payment Settled in the foreign currency.
See SS, CZK is not in the channel.
I've tested with Mollie and Stripe it both works.

Further notes

After looking into this further and with help from the comments below, the root cause of this vulnerability is the ability to specify an arbitrary currencyCode as a query parameter to an API call, and then Vendure will use this and pass it to the rest of the system as RequestContext.currencyCode.

The solution is to add validation to the passed currencyCode to ensure that it matches one of the available availableCurrencyCodes of the active Channel.

Furthermore, an additional check has been added for when the currencyCode changes during the AddingItems stage - in this case we need to re-calculate the prices in the new currency.

GHSA-WM63-7627-CH33 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.1.3); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

v2.1.3

1. What is GHSA-WM63-7627-CH33? GHSA-WM63-7627-CH33 is a medium-severity security vulnerability in @vendure/core (npm), affecting versions < 2.1.3. It is fixed in 2.1.3.
2. How severe is GHSA-WM63-7627-CH33? GHSA-WM63-7627-CH33 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of @vendure/core are affected by GHSA-WM63-7627-CH33? @vendure/core (npm) versions < 2.1.3 is affected.
4. Is there a fix for GHSA-WM63-7627-CH33? Yes. GHSA-WM63-7627-CH33 is fixed in 2.1.3. Upgrade to this version or later.
5. Is GHSA-WM63-7627-CH33 exploitable, and should I be worried? Whether GHSA-WM63-7627-CH33 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-WM63-7627-CH33 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-WM63-7627-CH33? Upgrade @vendure/core to 2.1.3 or later.

Other vulnerabilities in @vendure/core