NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

Diavante vue-storefront-api and storefront-api disclose stack traceGHSA-9wxj-37p8-49ff

MEDIUMFix: DivanteLtd/storefront-api#59

GHSA-9wxj-37p8-49ff is a medium-severity (CVSS 5.3) CWE-209 vulnerability in storefront-api. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for storefront-api — see the affected versions and patch details below.

Also known asCVE-2020-11883
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known
Exploitation data as of Oct 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
15.2%probability of exploitation in next 30 days
Moderate Risk0.00%
Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk
0.00%6.29%12.6%18.9%2.7%15.2%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
📦storefront-api📦vue-storefront-api

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

In Divante vue-storefront-api through 1.11.1 and storefront-api through 1.0-rc.1, as used in VueStorefront PWA, unexpected HTTP requests lead to an exception that discloses the error stack trace, with absolute file paths and Node.js module names.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npmstorefront-apiall versions1.0.0-rc3npm install storefront-api@1.0.0-rc3
📦npmvue-storefront-apiall versions1.12.0npm install vue-storefront-api@1.12.0

Affected Products

2 products · 2 configurations
Application
storefront-apidivante
1 version
1.0
Application
vue-storefront-apidivante
≤ 1.11.1
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

In Divante vue-storefront-api through 1.11.1 and storefront-api through …

github.comNVDJul 2021

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update storefront-api to 1.0.0-rc3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9wxj-37p8-49ff is resolved across your whole dependency graph.

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

In Divante vue-storefront-api through 1.11.1 and storefront-api through 1.0-rc.1, as used in VueStorefront PWA, unexpected HTTP requests lead to an exception that discloses the error stack trace, with absolute file paths and Node.js module names.
O3 Security · Impact-Aware SCA

Is GHSA-9wxj-37p8-49ff in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Diavante vue-storefront-api and storefront-api disclose…