Skip to content
Fencer Intel
medium 6.1

CVE-2020-7680 json

Cross-site Scripting in docsify

published 6y ago modified last mo. also GHSA-qpqh-46qj-vwcw , EUVD-2021-1169

cvss
6.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.5%
EPSS 4.5% chance of exploitation in 30 days, percentile 91%
public exploits
1
Exploit-DB

Summary

docsify prior to 4.11.4 is susceptible to Cross-site Scripting (XSS). Docsify.js uses fragment identifiers (parameters after # sign) to load resources from server-side .md files. Due to lack of validation here, it is possible to provide external URLs after the /#/ (domain.com/#//attacker.com) and render arbitrary JavaScript/HTML inside docsify page.

Patch / fix

  • npm docsify 4.11.4
  • docsifyjs docsify 4.11.4

Is CVE-2020-7680 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. Published
  2. First public exploit (EDB-48681)

Exploit prediction

4.50% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-48681 Docsify.js 4.11.4 - Reflective Cross-Site Scripting webapps, 2020-07-22
  • packetstormsecurity.com http://packetstormsecurity.com/files/158515/Docsify.js-4.11.4-Cross-Site-Scripting.html referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/161495/docsify-4.11.6-Cross-Site-Scripting.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N
GitHub 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
npm docsify
<4.11.4
4.11.4

Affected products

  • n/a docsify

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.