How severe is CVE-2020-28487?

CVE-2020-28487 has a CVSS score of 6.8/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2020-28487?

CVE-2020-28487 affects the following packages: vis-timeline (npm). Ecosystems affected: npm.

How do I fix CVE-2020-28487?

Update vis-timeline to 7.4.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-28487 is resolved across your whole dependency graph.

How do I detect CVE-2020-28487 in my npm dependencies?

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

How do I mitigate CVE-2020-28487 if there is no patch (or I can't update yet)?

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.

Is CVE-2020-28487 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2020-28487, including 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2020-28487?

CVE-2020-28487 has an EPSS (Exploit Prediction Scoring System) score of 1.4%, placing it in the 73th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2020-28487 published, and has it been updated?

CVE-2020-28487 was published on January 22, 2021 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

MEDIUM severity

CVE-2020-28487 — vis-timeline

MEDIUMFix: visjs/vis-timeline#840

CVE-2020-28487 is a medium-severity (CVSS 6.8) vulnerability in vis-timeline. 3 public exploit references exist, so weaponization risk is real. A fix is available for vis-timeline — see the affected versions and patch details below.

Cross-site Scripting in vis-timeline

Also known asGHSA-9mrv-456v-pf22

Published

Jan 22, 2021

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

3 known

Exploitation data as of Oct 11, 2026 · OSV.dev, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs73th percentile — riskier than 73% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2020-28487 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

69other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

vis-timelinenpm

251Kdownloads / week

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

Ecosystem	Package	Vulnerable range	Fix
📦npm	`vis-timeline`	all versions	7.4.4`npm install vis-timeline@7.4.4`

Exploits & PoCs

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

This affects the package vis-timeline before 7.4.4. An attacker with the…

snyk.ioNVDFeb 2021

This affects the package vis-timeline before 7.4.4. An attacker with the…

snyk.ioNVDFeb 2021

This affects the package vis-timeline before 7.4.4. An attacker with the…

snyk.ioNVDFeb 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vis-timeline, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update vis-timeline to 7.4.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-28487 is resolved across your whole dependency graph.
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

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 CVE-2020-28487 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2020-28487 — vis-timeline

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2020-28487 in your dependencies?