Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-5h7x-68wj-jhwc

MEDIUMFix: docsifyjs/docsify#1551

GHSA-5h7x-68wj-jhwc is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in docsify. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-5h7x-68wj-jhwc is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Docsify vulnerable to cross-site scripting due to mishandled encoding

Also known asCVE-2021-30074
Published
May 24, 2022
Updated
Nov 8, 2023
Affected
1 pkg
Patched
1 / 1
Exploits
1 known

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

docsifynpm
136Kdownloads / week

Description

docsify versions 4.12.1 and earlier are vulnerable to cross-site scripting (XSS) because the search component does not appropriately encode Code Blocks and mishandles the " character.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmdocsifyall versions4.12.2
Exploits & PoCs
1

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 docsify. 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 docsify to 4.12.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5h7x-68wj-jhwc 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-5h7x-68wj-jhwc 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-5h7x-68wj-jhwc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

docsify versions 4.12.1 and earlier are vulnerable to cross-site scripting (XSS) because the search component does not appropriately encode Code Blocks and mishandles the `"` character.
O3 Security · Impact-Aware SCA

Is GHSA-5h7x-68wj-jhwc in your dependencies?

O3 detects GHSA-5h7x-68wj-jhwc across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.