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

GHSA-9mrv-456v-pf22

MEDIUMFix: visjs/vis-timeline#840

GHSA-9mrv-456v-pf22 is a medium-severity (CVSS 6.8) Cross-site Scripting (XSS) vulnerability in vis-timeline. 3 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-9mrv-456v-pf22 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Cross-site Scripting in vis-timeline

Also known asCVE-2020-28487
Published
Apr 13, 2021
Updated
Jan 14, 2025
Affected
1 pkg
Patched
1 / 1
Exploits
3 known
Exploitation data as of Jan 14, 2025 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
📦vis-timeline

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

This affects the package vis-timeline before 7.4.4. An attacker with the ability to control the items of a Timeline element can inject additional script code into the generated application.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmvis-timelineall versions7.4.4
Exploits & PoCs
3

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

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vis-timeline. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update vis-timeline to 7.4.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9mrv-456v-pf22 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 pinpoints whether GHSA-9mrv-456v-pf22 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-9mrv-456v-pf22. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

This affects the package vis-timeline before 7.4.4. An attacker with the ability to control the items of a Timeline element can inject additional script code into the generated application.
O3 Security · Impact-Aware SCA

Is GHSA-9mrv-456v-pf22 in your dependencies?

O3 detects GHSA-9mrv-456v-pf22 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-9mrv-456v-pf22: Cross-site Scripting in… | O3 Security