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

CVE-2021-4103

MEDIUM

CVE-2021-4103 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in vditor. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2021-4103 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

vditor Vulnerable to Cross-site Scripting in SVG events

Also known asGHSA-cxm3-v4mv-6mh8
Published
Jan 23, 2022
Updated
Jul 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
1 known

Blast Radius

1 pkg affected
📦vditor

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Cross-site Scripting (XSS) - Stored in GitHub repository vanessa219/vditor prior to 1.0.34.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmvditorall versions3.8.11
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 vditor. 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 vditor to 3.8.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-4103 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 CVE-2021-4103 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 CVE-2021-4103. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Cross-site Scripting (XSS) - Stored in GitHub repository vanessa219/vditor prior to 1.0.34.
O3 Security · Impact-Aware SCA

Is CVE-2021-4103 in your dependencies?

O3 detects CVE-2021-4103 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.