CVE-2020-11023

CRITICALNVD 6.99.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2025-01-23), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 6.9 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Trending — 3 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 85%CVSS: 6.9Exploit: cisa kev · ssvc active · epss top5pct · epss high · public exploitExposed services: Not assessed

A fix is available — apply it.

In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing 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.

CVSS v3
6.9
EG Score
9.0CRITICALhigh confidence
EG Risk
81
EG Risk 81/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
85%
EPSS %ILE
99th
KEV
⚠ Exploited

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

April 29, 2020

Last Modified

November 7, 2025

Advisory Details (6)

Auto-updated Jun 12, 2026
Patch available. Sources: github.
generic
https://lists.apache.org/thread.html/r07ab379471fb15644bf7a92e4a98cbc7df3cf4e736abae0cc7625fe6%40%3Cdev.felix.apache.org%3E
generic
https://lists.apache.org/thread.html/r0593393ca1e97b1e7e098fe69d414d6bd0a467148e9138d07e86ebbb%40%3Cissues.hive.apache.org%3E
generic
https://lists.apache.org/thread.html/r0483ba0072783c2e1bfea613984bfb3c86e73ba8879d780dc1cc7d36%40%3Cissues.flink.apache.org%3E
generic

jQuery Core 3.5 Upgrade Guide | jQuery

https://jquery.com/upgrade-guide/3.5/
githubMentions a patch (unverified)

Potential XSS vulnerability when appending HTML containing option elements · Advisory · jquery/jquery · GitHub

https://github.com/jquery/jquery/security/advisories/GHSA-jpcq-cgw6-v4j6
generic

jQuery 3.5.0 Released! | Official jQuery Blog

https://blog.jquery.com/2020/04/10/jquery-3-5-0-released

Vendor Advisories for CVE-2020-11023(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpki-core-0:10.5.16-8.el7_72025-03-06redhat
redhatopenshift-logging/kibana6-rhel8:v6.8.1-4792025-03-05redhat
redhatquay/quay-rhel8:v3.9.10-72025-02-24redhat
redhatquay/quay-rhel8:v3.11.9-52025-02-24redhat
redhatquay/quay-rhel8:v3.10.9-22025-02-24redhat
redhatquay/quay-rhel8:v3.13.4-62025-02-24redhat
redhatquay/quay-rhel8:v3.12.8-22025-02-24redhat
redhatgcc-0:4.8.5-40.el7_72025-02-17redhat
redhatidm:DL1-8020020250212111622.792f40602025-02-17redhat
redhatgcc-0:4.8.5-45.el7_92025-02-17redhat
redhatipa-0:4.6.5-11.el7_7.52025-02-17redhat
redhatgcc-toolset-14-gcc-0:14.2.1-7.1.el8_102025-02-12redhat
redhatgcc-0:11.5.0-5.el9_52025-02-12redhat
redhatgcc-toolset-13-gcc-0:13.3.1-2.2.el9_42025-02-12redhat
redhatgcc-0:11.2.1-9.5.el9_02025-02-11redhat
redhatgcc-0:8.3.1-8.el8_22025-02-11redhat
redhatgcc-0:8.5.0-23.el8_102025-02-11redhat
redhatgcc-0:8.5.0-18.3.el8_82025-02-11redhat
redhatdoxygen-1:1.9.1-12.el9_42025-02-11redhat
redhatgcc-toolset-13-gcc-0:13.3.1-2.2.el8_102025-02-11redhat
redhatgcc-0:11.4.1-4.el9_42025-02-11redhat
redhatdoxygen-1:1.9.1-12.el9_52025-02-11redhat
redhatgcc-toolset-13-gcc-0:13.3.1-2.2.el9_52025-02-11redhat
redhatgcc-toolset-14-gcc-0:14.2.1-1.3.el9_52025-02-11redhat
redhatdoxygen-1:1.8.14-13.el8_102025-02-11redhat
redhatgcc-0:8.4.1-1.4.el8_42025-02-11redhat
redhatgcc-0:8.5.0-10.4.el8_62025-02-11redhat
redhatgcc-0:11.3.1-4.4.el9_22025-02-11redhat
redhattbb-0:2020.3-8.el9_4.12025-02-10redhat
redhattbb-0:2018.2-10.el8_6.12025-02-10redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(16 across 11 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
node-jquery—
  • every version up to 3.5.0+dfsg-2: fixed in 3.5.0+dfsg-2
—
otrs22.0.4p01-10 ... 6.0.9-1~bpo9+1 (244 versions)
  • every version up to 6.0.30-1: fixed in 6.0.30-1
—
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
node-jquery—
  • every version up to 3.5.0+dfsg-2: fixed in 3.5.0+dfsg-2
—
znc1.10.1-1 ... 1.9.1-2 (10 versions)
  • every version on: no fix on record
—
Debian:13(2)
PackageVulnerable rangeFix by version rangeDependents
node-jquery—
  • every version up to 3.5.0+dfsg-2: fixed in 3.5.0+dfsg-2
—
znc1.10.1-1, 1.10.2-1, 1.10.3-1, 1.9.1-2, 1.9.1-2+deb13u1
  • every version on: no fix on record
—
Debian:14(2)
PackageVulnerable rangeFix by version rangeDependents
node-jquery—
  • every version up to 3.5.0+dfsg-2: fixed in 3.5.0+dfsg-2
—
znc1.10.1-1, 1.10.2-1, 1.9.1-2
  • every version up to 1.10.3-1: fixed in 1.10.3-1
—
Debian:9(2)
PackageVulnerable rangeFix by version rangeDependents
drupal77.52-2 ... 7.52-2+deb9u9 (10 versions)
  • every version up to 7.52-2+deb9u10: fixed in 7.52-2+deb9u10
—
jquery3.1.1-2, 3.1.1-2+deb9u1
  • every version up to 3.1.1-2+deb9u2: fixed in 3.1.1-2+deb9u2
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
otrs22.0.4p01-10 ... 6.0.9-1~bpo9+1 (219 versions)
  • every version up to 6.0.16-2+deb10u1: fixed in 6.0.16-2+deb10u1
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.webjars.npm:jquery1.11.0 ... 3.4.1 (35 versions)
  • 1.0.3 up to 3.5.0: fixed in 3.5.0
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
jquery—
  • 1.0.3 up to 3.5.0: fixed in 3.5.0
—
NuGet(1)
PackageVulnerable rangeFix by version rangeDependents
jQuery1.10.0 ... 3.4.1 (58 versions)
  • 1.0.3 up to 3.5.0: fixed in 3.5.0
—
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
components/jquery1.10.0 ... 3.4.1 (31 versions)
  • 1.0.3 up to 3.5.0: fixed in 3.5.0
—
RubyGems(1)
PackageVulnerable rangeFix by version rangeDependents
jquery-rails0.1.1 ... 4.3.5 (74 versions)
  • every version up to 4.4.0: fixed in 4.4.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(20)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 52× in last 7d / 233× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 1,011 total refreshes for this CVE.

  1. 2026-10-10 05:50 UTCVendor advisory
  2. 2026-10-10 02:02 UTCVendor advisory
  3. 2026-10-09 22:14 UTCEG score recompute
  4. 2026-10-09 22:14 UTCVendor advisory
  5. 2026-10-09 20:03 UTCEPSS rescore
  6. 2026-10-09 18:26 UTCVendor advisory
  7. 2026-10-09 14:34 UTCVendor advisory
  8. 2026-10-09 10:44 UTCVendor advisory
  9. 2026-10-09 06:53 UTCVendor advisory
  10. 2026-10-09 03:05 UTCVendor advisory
  11. 2026-10-08 23:16 UTCVendor advisory
  12. 2026-10-08 19:29 UTCEG score recompute
  13. 2026-10-08 19:29 UTCVendor advisory
  14. 2026-10-08 16:38 UTCEPSS rescore
  15. 2026-10-08 15:41 UTCVendor advisory
  16. 2026-10-08 11:53 UTCVendor advisory
  17. 2026-10-08 08:05 UTCVendor advisory
  18. 2026-10-08 04:16 UTCVendor advisory
  19. 2026-10-08 00:28 UTCEG score recompute
  20. 2026-10-08 00:28 UTCVendor advisory
  21. 2026-10-07 23:43 UTCEPSS rescore
  22. 2026-10-07 20:40 UTCVendor advisory
  23. 2026-10-07 16:53 UTCVendor advisory
  24. 2026-10-07 13:02 UTCVendor advisory
  25. 2026-10-07 09:14 UTCVendor advisory
Show 75 more
  1. 2026-10-07 05:26 UTCVendor advisory
  2. 2026-10-07 01:38 UTCVendor advisory
  3. 2026-10-06 21:50 UTCVendor advisory
  4. 2026-10-06 18:02 UTCVendor advisory
  5. 2026-10-06 14:14 UTCVendor advisory
  6. 2026-10-06 10:26 UTCVendor advisory
  7. 2026-10-06 06:39 UTCVendor advisory
  8. 2026-10-06 02:46 UTCVendor advisory
  9. 2026-10-05 22:57 UTCVendor advisory
  10. 2026-10-05 19:09 UTCEG score recompute
  11. 2026-10-05 19:09 UTCVendor advisory
  12. 2026-10-05 17:39 UTCEPSS rescore
  13. 2026-10-05 15:21 UTCVendor advisory
  14. 2026-10-05 11:33 UTCVendor advisory
  15. 2026-10-05 07:45 UTCVendor advisory
  16. 2026-10-05 03:57 UTCVendor advisory
  17. 2026-10-05 00:09 UTCVendor advisory
  18. 2026-10-04 20:20 UTCVendor advisory
  19. 2026-10-04 16:29 UTCVendor advisory
  20. 2026-10-04 12:41 UTCVendor advisory
  21. 2026-10-04 08:53 UTCVendor advisory
  22. 2026-10-04 05:04 UTCVendor advisory
  23. 2026-10-04 01:17 UTCVendor advisory
  24. 2026-10-03 21:29 UTCVendor advisory
  25. 2026-10-03 17:41 UTCVendor advisory
  26. 2026-10-03 13:53 UTCVendor advisory
  27. 2026-10-03 10:03 UTCVendor advisory
  28. 2026-10-03 06:15 UTCVendor advisory
  29. 2026-10-03 02:27 UTCVendor advisory
  30. 2026-10-02 22:39 UTCVendor advisory
  31. 2026-10-02 18:51 UTCEG score recompute
  32. 2026-10-02 18:51 UTCVendor advisory
  33. 2026-10-02 15:03 UTCVendor advisory
  34. 2026-10-02 11:16 UTCVendor advisory
  35. 2026-10-02 07:27 UTCVendor advisory
  36. 2026-10-02 03:40 UTCVendor advisory
  37. 2026-10-01 23:52 UTCVendor advisory
  38. 2026-10-01 20:02 UTCVendor advisory
  39. 2026-10-01 16:14 UTCVendor advisory
  40. 2026-10-01 12:26 UTCVendor advisory
  41. 2026-10-01 08:37 UTCVendor advisory
  42. 2026-10-01 04:50 UTCVendor advisory
  43. 2026-10-01 00:59 UTCVendor advisory
  44. 2026-09-30 21:11 UTCVendor advisory
  45. 2026-09-30 17:23 UTCVendor advisory
  46. 2026-09-30 13:36 UTCVendor advisory
  47. 2026-09-30 09:47 UTCVendor advisory
  48. 2026-09-30 06:00 UTCVendor advisory
  49. 2026-09-30 02:12 UTCVendor advisory
  50. 2026-09-29 22:25 UTCVendor advisory
  51. 2026-09-29 18:36 UTCVendor advisory
  52. 2026-09-29 14:47 UTCVendor advisory
  53. 2026-09-29 10:58 UTCVendor advisory
  54. 2026-09-29 07:10 UTCVendor advisory
  55. 2026-09-29 03:20 UTCVendor advisory
  56. 2026-09-28 23:32 UTCEG score recompute
  57. 2026-09-28 23:32 UTCVendor advisory
  58. 2026-09-28 19:44 UTCVendor advisory
  59. 2026-09-28 15:53 UTCVendor advisory
  60. 2026-09-28 12:05 UTCVendor advisory
  61. 2026-09-28 08:17 UTCVendor advisory
  62. 2026-09-28 04:29 UTCVendor advisory
  63. 2026-09-28 00:41 UTCVendor advisory
  64. 2026-09-27 21:51 UTCCISA KEV update
  65. 2026-09-27 20:53 UTCVendor advisory
  66. 2026-09-27 17:05 UTCEG score recompute
  67. 2026-09-27 17:05 UTCVendor advisory
  68. 2026-09-27 13:40 UTCEPSS rescore
  69. 2026-09-27 13:18 UTCVendor advisory
  70. 2026-09-27 09:30 UTCVendor advisory
  71. 2026-09-27 05:42 UTCVendor advisory
  72. 2026-09-27 01:54 UTCVendor advisory
  73. 2026-09-26 22:03 UTCVendor advisory
  74. 2026-09-26 18:16 UTCEG score recompute
  75. 2026-09-26 18:16 UTCVendor advisory

Publicly available exploits

(3 references)

Working exploit code is in the public domain (2 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoChoneyb33z/cve-2020-11023-scanner
    First seen Jan 30, 2025
    Open source ↗
  • GitHub PoCCybernegro/CVE-2020-11023
    First seen Jan 3, 2024

    CVE-2020-11023 PoC for bug bounty.

    Open source ↗
  • Exploit-DBEDB-49767
    First seen Apr 14, 2021

    jQuery 1.0.3 - Cross-Site Scripting (XSS)

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Frequently asked(6)

What is CVE-2020-11023?
CVE-2020-11023 is a critical vulnerability published on April 29, 2020. 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…
When was CVE-2020-11023 disclosed?
CVE-2020-11023 was first published on April 29, 2020, with the most recent update on November 7, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-11023 actively exploited?
Yes. CISA added CVE-2020-11023 to the Known Exploited Vulnerabilities catalog on January 23, 2025, affecting JQuery JQuery. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2020-11023?
CVE-2020-11023 has a CVSS v3 base score of 6.9 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2020-11023?
CVE-2020-11023 affects JQuery JQuery. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2020-11023?
A fix for CVE-2020-11023 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2020-11023 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-11023

Explore →

Is Your Infrastructure Affected by CVE-2020-11023?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs