Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm
Not in CISA KEV

GHSA-cfxh-frx4-9gjg @spscommerce/ds-react

GHSA-cfxh-frx4-9gjg is a security vulnerability in @spscommerce/ds-react. A fix is available for @spscommerce/ds-react — see the affected versions and patch details below.

Cross-site Scripting in @spscommerce/ds-react

Published
Dec 15, 2023
Updated
Dec 15, 2023
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Dec 15, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
📦@spscommerce/ds-react

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

Impact

XSS, anyone using the SPS Select with options prop populated from user input is impacted. If these options are stored, then it could have been a stored XSS.

Patches

The code has been patched for version 7 of woodland. Users should upgrade to 7.17.4 or higher

Workarounds

This is not recommended. If you are not upgrading then you would need to sanitize your options yourself (including those currently stored in databases). This is not recommended.

References

https://github.com/SPSCommerce/woodland/blob/c49e999f97f3c0b56502859f4de1e8c6666dd74d/packages/ds-react/src/option-list/SpsOptionList.tsx#L559

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npm@spscommerce/ds-react4.12.2&&< 7.17.47.17.4npm install @spscommerce/ds-react@7.17.4

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update @spscommerce/ds-react to 7.17.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cfxh-frx4-9gjg 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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-cfxh-frx4-9gjg can be triaged on real exposure rather than presence alone.

Tailored to GHSA-cfxh-frx4-9gjg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact XSS, anyone using the SPS Select with options prop populated from user input is impacted. If these options are stored, then it could have been a stored XSS. ### Patches The code has been patched for version 7 of woodland. Users should upgrade to 7.17.4 or higher ### Workarounds This is not recommended. If you are not upgrading then you would need to sanitize your options yourself (including those currently stored in databases). This is not recommended. ### References https://github.com/SPSCommerce/woodland/blob/c49e999f97f3c0b56502859f4de1e8c6666dd74d/packages/ds-react/src/optio
O3 Security · Impact-Aware SCA

Is GHSA-cfxh-frx4-9gjg in your dependencies?

O3 Security finds GHSA-cfxh-frx4-9gjg across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-cfxh-frx4-9gjg: @spscommerce/ds XSS | O3 Security