JQuery Cross-Site Scripting (XSS) Vulnerability
jquery — jQuery
In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements 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.
6.9
83.8%
Vector breakdown
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:N
- Published
- Apr 29, 2020
- Modified
- Jun 17, 2026
- Added to KEV
- Jan 23, 2025
- Federal patch due
- Feb 13, 2025
CISA required action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Weakness classification
Affected packages
Proof-of-concept & exploitation references
8 foundWeaponization
Public repositories whose name or description references CVE-2020-11023, found via a live GitHub search at request time. These are community-sourced signals, not a verified working exploit - cross-check each one before relying on it, and treat higher star counts and recent activity as (weak) corroboration, not proof.
- 0xAJ2K/CVE-2020-11022-CVE-2020-11023★ 34
Little thing put together quickly to demonstrate this CVE
updated Oct 12, 2026
- DanielRuf/snyk-js-jquery-565129★ 27
patches for SNYK-JS-JQUERY-565129, SNYK-JS-JQUERY-567880, CVE-2020-1102, CVE-2020-11023, includes the patches for SNYK-JS-JQUERY-174006, CVE-2019-11358, CVE-2019-5428
updated Sep 29, 2025
- Cybernegro/CVE-2020-11023★ 4
CVE-2020-11023 PoC for bug bounty.
updated Aug 25, 2026
- honeyb33z/cve-2020-11023-scanner★ 4
updated Aug 10, 2026
- Snorlyd/https-nj.gov---CVE-2020-11023★ 1
Vulnearability Report of the New Jersey official site
updated Mar 22, 2024
- GarlicB/jquery35-local-agent★ 1
Offline jQuery CVE-2020-11023 remediation kit for legacy Spring/JSP - Node.js built-ins only (no npm, no internet)
updated Jul 31, 2026
- andreassundstrom/cve-2020-11023-demonstration★ 0
Demonstration of CVE-2020-11023
updated Apr 13, 2024
- asoka666/Cve-2020-11023★ 0
updated Jul 14, 2026
References
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- packetstormsecurity.com
- blog.jquery.com
- github.com
- jquery.com
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
- lists.apache.org
How this class of flaw gets exploited
Frequently asked questions
What is CVE-2020-11023?
In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements 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.
How severe is CVE-2020-11023?
CVE-2020-11023 has a CVSS base score of 6.9 out of 10 (CVSS 3.1).
Is CVE-2020-11023 actively exploited in the wild?
Yes. CVE-2020-11023 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added Jan 23, 2025, meaning CISA has confirmed evidence of active exploitation.
What is the EPSS score for CVE-2020-11023?
83.8% - meaning FIRST.org's EPSS model estimates a 83.8% probability this vulnerability will be exploited in the wild within 30 days (100% percentile among all scored CVEs).
Is there exploit tooling available for CVE-2020-11023?
We found 8 public GitHub repositories referencing CVE-2020-11023, though none matched a known Nuclei template or Metasploit module at last check. Review each one before relying on it - see the proof-of-concept section above.
What type of vulnerability is CVE-2020-11023?
CVE-2020-11023 is classified under CWE-79 (CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')).
Cross-checked against
Impactr finds and proves whether CVE-2020-11023 - or flaws like it - are actually reachable in your own web apps and APIs, with a reproducible exploit as evidence.
Join the waitlist