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

CVE-2016-1000241 — pivottable

Fix: nicolaskruchten/pivottable#401

CVE-2016-1000241 is a security vulnerability in pivottable. A fix is available for pivottable — see the affected versions and patch details below.

Cross-Site Scripting (XSS) in pivottable

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

Real-World Exposure

1 pkg affected
📦pivottable

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

Affected versions of pivottable are vulnerable to cross-site scripting, due to a new mechanism used to render JSON elements.

Recommendation

Update to version 2.0.0 or later.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmpivottable≥ 1.4.0&&< 2.0.02.0.0npm install pivottable@2.0.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update pivottable to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-1000241 is resolved across your whole dependency graph.

  3. Workarounds

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

Affected versions of `pivottable` are vulnerable to cross-site scripting, due to a new mechanism used to render JSON elements. ## Recommendation Update to version 2.0.0 or later.
O3 Security · Impact-Aware SCA

Is CVE-2016-1000241 in your dependencies?

Find it across npm, including transitive dependencies.