CVE-2020-11022
MEDIUMCVE-2020-11022 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in org.webjars.npm:jquery. 8 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2020-11022 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Potential XSS vulnerability in jQuery
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
jquerynpmDescription
In jQuery starting with 1.12.0 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.webjars.npm:jquery | ≥ 1.12.0&&< 3.5.0 | 3.5.0 |
| 📦npm | jquery | ≥ 1.12.0&&< 3.5.0 | 3.5.0 |
| .NETNuGet | jquery | ≥ 1.12.0&&< 3.5.0 | 3.5.0 |
| 🐘Packagist | maximebf/debugbar | all versions | 1.19.0 |
| 🐘Packagist | athlon1600/youtube-downloader | all versions | 4.0.1 |
| 🐘Packagist | components/jquery | ≥ 1.12.0&&< 3.5.0 | 3.5.0 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
jQuery 1.2 - Cross-Site Scripting (XSS)
by Central InfoSec · Apr 14, 2021
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.webjars.npm:jquery. 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.
Fix
Update org.webjars.npm:jquery to 3.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-11022 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether CVE-2020-11022 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-2020-11022. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2020-11022 in your dependencies?
O3 detects CVE-2020-11022 across Maven, npm, NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.