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

CVE-2020-7691 — jspdf

MEDIUMFix: MrRio/jsPDF@d032321

CVE-2020-7691 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in jspdf. 5 public exploit references exist, so weaponization risk is real. A fix is available for jspdf — see the affected versions and patch details below.

Cross-site scripting in jspdf

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
5 known
Exploitation data as of Oct 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs75th percentile — riskier than 75% of all scored CVEsHighest risk
0.00%0.69%1.38%2.07%0.2%1.6%Apr 26Aug 26Oct 26

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

How urgent is this, really

CVE-2020-7691 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.

3Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
jspdfnpm
16.0Mdownloads / week

Description

In all versions of the package jspdf, it is possible to use <<script>script> in order to go over the filtering regex.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmjspdfall versions2.0.0npm install jspdf@2.0.0

Affected Products

1 product · 1 configurations
Application
jspdfparall
all
Exploits & PoCs
5

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 jspdf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update jspdf to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-7691 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

It's possible to use nested script tags in order to bypass the filtering regex.
O3 Security · Impact-Aware SCA

Is CVE-2020-7691 in your dependencies?

Find it across npm, including transitive dependencies.

CVE-2020-7691: jspdf — Fixed in 2.0.0