jQuery XSS via DOM manipulation of untrusted HTML containing <option> elements
In jQuery versions >= 1.0.3 and < 3.5.0, passing HTML containing <option> elements from untrusted sources to jQuery DOM manipulation methods such as .html(), .append(), and related APIs can result in execution of untrusted script in the browser. The issue persists even when the HTML has been sanitized in ways that are not safe for jQuery’s parsing behavior. The vulnerability is an improper neutralization of untrusted input during client-side HTML handling, leading to a cross-site scripting condition. The issue was patched in jQuery 3.5.0.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (4 hidden).
This repository is a proof-of-concept (POC) environment for demonstrating CVE-2020-11023, a cross-site scripting (XSS) vulnerability in jQuery 3.4.1. The repository contains a Dockerfile and docker-compose.yml for easy setup of a vulnerable PHP web application. The main application (src/index.php) accepts user input via POST and directly injects it into the DOM using jQuery's .html() method, which is vulnerable to XSS. The README provides example payloads and mitigation strategies. The application is intended for educational and testing purposes only, and should not be used in production. The main exploit capability is browser-based XSS via injection of arbitrary JavaScript. The main endpoints are the local web server (http://localhost:8080) and the externally loaded jQuery library.
This repository is a proof-of-concept exploit for CVE-2020-11022 and CVE-2020-11023, which are cross-site scripting (XSS) vulnerabilities in jQuery versions prior to 3.5.0. The repository contains two files: a README.md with detailed exploitation instructions and an index.php file that serves as a vulnerable web application. The exploit demonstrates how an attacker can inject arbitrary JavaScript via the 'value' URL parameter, leading to XSS and cookie theft. The attack is performed by hosting index.php on a PHP webserver with a vulnerable jQuery version, then visiting a crafted URL and triggering DOM manipulation via a button. The exploit also shows how to exfiltrate cookies to an attacker-controlled server. The repository is structured as a simple, educational POC and does not include weaponized or automated exploitation features.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A medium-severity cross-site scripting (XSS) vulnerability in jQuery; noted as prevalent in codebases and listed in CISA’s Known Exploited Vulnerabilities (KEV) catalog.
jQuery cross-site scripting vulnerability; added to CISA KEV indicating active exploitation.
A cross-site scripting vulnerability in jQuery related to improper validation of option elements.
A vulnerability in the jQuery dependency (as used by Adobe Experience Manager) described as enabling arbitrary code execution, affecting AEM 6.5.7.0 and earlier.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.