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

CVE-2020-28470 — @scullyio/scully

HIGHFix: scullyio/scully#1182

CVE-2020-28470 is a high-severity (CVSS 7.3) Cross-site Scripting (XSS) vulnerability in @scullyio/scully. A fix is available for @scullyio/scully — see the affected versions and patch details below.

Cross-site Scripting (XSS) in @scullyio/scully

Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Oct 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs56th percentile — riskier than 56% of all scored CVEsHighest risk
0.00%0.44%0.88%1.33%0.3%0.8%Apr 26Aug 26Oct 26

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

How urgent is this, really

CVE-2020-28470 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

2 pkgs 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.

4other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
@scullyio/scullynpm
3Kdownloads / week
@scullyio/ng-libnpm
2Kdownloads / week

Description

This affects the package @scullyio/scully before 1.0.9. The transfer state is serialised with the JSON.stringify() function and then written into the HTML page.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npm@scullyio/scullyall versions1.0.9npm install @scullyio/scully@1.0.9
📦npm@scullyio/ng-liball versions1.0.1npm install @scullyio/ng-lib@1.0.1

Affected Products

1 product · 1 configurations
Application
scullyscully
< 1.0.9
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update @scullyio/scully to 1.0.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-28470 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

This affects the package @scullyio/scully before 1.0.9. The transfer state is serialised with the JSON.stringify() function and then written into the HTML page.
O3 Security · Impact-Aware SCA

Is CVE-2020-28470 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-28470: @scullyio/scully — Fixed in 1.0.9