Is there a public exploit for CVE-2020-11022?

Yes. An exploit for CVE-2020-11022 is archived and downloadable from Exploit-DB.

Is there a proof of concept for CVE-2020-11022?

Yes — 3 proof-of-concept entries are linked on this page, from public repositories and community submissions. They are listed for authorised testing only.

How severe is CVE-2020-11022?

CVE-2020-11022 scores CVSS 6.9 (v3.1), rated medium. EPSS puts the chance of exploitation in the next 30 days at 99.22%.

What does CVE-2020-11022 affect?

CVE-2020-11022 affects jquery jQuery.

6.9 Medium

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…

CVE-2020-11022

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.

A public exploit is available

Exploit-DB · Public PoC

Exploit-DBjQuery 1.2 - Cross-Site Scripting (XSS)
Public PoC0xAJ2K/CVE-2020-11022-CVE-2020-1102334 stars
Public PoCSnorlyd/https-nj.gov---CVE-2020-110221 stars
Public PoCokni2k/HW-Pyton-10

Signals come from Exploit-DB, Metasploit, Nuclei and published proof-of-concept repositories. Their absence means nothing was found, not that nothing exists.

Assessment

CVSS: 6.9 (v3.1)
Severity: Medium
EPSS: 99.22% chance of exploitation in the next 30 days
Known exploited: Not listed in CISA KEV
Exploit availability: Exploit-DB, Public PoC
Published: 29 April 2020
Last updated: 2 November 2026
Affected: jquery · jQuery
Assigner: GitHub_M

CVSS vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:N

At the source

EUVD (ENISA)

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 8 + 8? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2020-11022